-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Dev] Allow passing --progress=plain
to archery docker build
#43669
Comments
(cc @assignUser @raulcd to check whether this makes sense, or if there are better ways to see verbose output and printing from the build stage) |
Sounds sensible 👍 |
Probably not well documented but from my understanding
|
ok, this was added not long ago (#40129), we should probably document it. |
That indeed seems to be what I wanted! |
I will look into adding that to the dev docs. But the CLI help, it is actually kind of documented in the top-level one:
assuming those options listed are available for all subcommands. But when you are looking at the specific options for docker build, that doesn't show up, so it is easy to miss:
|
…docker (#43935) ### Rationale for this change This feature was added in #40129, but adding it to the docker page in the developer docs for better visibility. * GitHub Issue: #43669 Authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
Issue resolved by pull request 43935 |
…about docker (apache#43935) ### Rationale for this change This feature was added in apache#40129, but adding it to the docker page in the developer docs for better visibility. * GitHub Issue: apache#43669 Authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
…about docker (apache#43935) ### Rationale for this change This feature was added in apache#40129, but adding it to the docker page in the developer docs for better visibility. * GitHub Issue: apache#43669 Authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com> Signed-off-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
I was debugging one of our docker-compose based CI build, and building and running the docker image locally with
archery docker build xxx
.As the documentation (https://arrow.apache.org/docs/dev/developers/continuous_integration/docker.html) mentions, you can specify
--no-cache
toarchery docker run/build
(which passes that todocker compose build
, but while debugging, I found that additionally it would have been helpful to be able to pass--progress=plain
through.The text was updated successfully, but these errors were encountered: