-
Notifications
You must be signed in to change notification settings - Fork 156
Collapse logging of run output by default #407
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
Collapse logging of run output by default #407
Conversation
8212330 to
2b30650
Compare
2b30650 to
1bfc082
Compare
pzeballos
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @francoiscampbell! I think this is reasonable, but you are changing the default behavior, if the default kept the current functionality will be ok to merge (and update the test 🙂 )
|
Ok @pzeballos, I've flipped the default. Are we OK with the default being inconsistent between this plugin and the Docker one? |
f83ba32 to
10b47e7
Compare
yep, all good, they are different plugins, and we prefer not to do a backwards compatibility change at the moment :) The build is failing in the linter step @francoiscampbell , can you update the Readme to use v4.15.0? Thanks! |
|
Updated |
pzeballos
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
By default this plugin collects the run output in a
+++group, while thedockerplugin collects it in a---group (https://github.com/buildkite-plugins/docker-buildkite-plugin/blob/36b85cc317745f868f2f6918a02f9cfb6a0b3069/commands/run.sh#L503). This PR unifies the two plugins by switching to using---by default.The rationale for using
---by default is that when we're passing lots of environment variables, volumes, etc, thedocker-compose run ...command gets pretty long and having the log group expanded by default is noisy. Additionally, it's quite likely that the command being run will create a+++group of its own, so it's not necessary for the plugin to provide one by default.For backwards compatibility, the
collapse-run-log-groupoption has been added, which will restore the old behaviour.