Replies: 1 comment
-
|
Bump ? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm currently trying to rewrite my old CI workflow using
build bakeand I think I missed something.Consider this dockerfile and this bake file:
In the
teststage of theDockerfile, I want to run sanity checks on the image produced in thereleasestage before publishing the image to the registry.However, if I run
build bake test release --push, the image is built and pushed before thetesttarget has a chance to run because there's a logical dependency between the stages in theDockerfilewhich prevents thetesttarget to run before the image is produced and the push happens in parallel.So what's the proper way to get the targets sequentially in this case? Is that a bug if the push happens before all the targets have finished their execution?
I suppose I can just run
build bake test && build bake release --pushto force my targets to be run sequentially. But since we can define somegroupin the bake file to run targets in parallel (which is equivalent to specifying many targets on the command line), i tend to thinkbuild bakeis missing an equivalent to run targets sequentially, e.g.What's your opinion about that?
Beta Was this translation helpful? Give feedback.
All reactions