You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably related to #165 (which I fully support) but as an FYI to others and a place to discuss fixes/workarounds, I'm opening this issue.
Previously, if you needed to run multiple commands (e.g. foo1 -x; bar2 -y), docker-compose-buildkite-plugin would parse this as docker-compose run image "foo1 -x"; bar2 -y (i.e. your second command didn't run in container).
My workaround in some cases has been to use heredocs:
I think, ultimately, these should probably be extracted out into separate scripts anyway, so this isn't a huge problem, but it probably is a good FYI for others and another command use-case that could have been tested to catch this.
The text was updated successfully, but these errors were encountered:
From what I can see, multi-line commands were added to unit tests of the plugin as well as the actual pipeline (see b96db48 ) to prevent regressions. Let us know if something is stll not working, though
Probably related to #165 (which I fully support) but as an FYI to others and a place to discuss fixes/workarounds, I'm opening this issue.
Previously, if you needed to run multiple commands (e.g.
foo1 -x; bar2 -y
),docker-compose-buildkite-plugin
would parse this asdocker-compose run image "foo1 -x"; bar2 -y
(i.e. your second command didn't run in container).My workaround in some cases has been to use heredocs:
These commands no longer parse with the command parsing change:
(example failing step for BK team: https://buildkite.com/covidence/app/builds/2767#65db24e2-c53a-433f-b826-3881bf9e0d19)
I think, ultimately, these should probably be extracted out into separate scripts anyway, so this isn't a huge problem, but it probably is a good FYI for others and another command use-case that could have been tested to catch this.
The text was updated successfully, but these errors were encountered: