ci: abort Docker build job when workflow is cancelled#6024
Merged
Conversation
gz
approved these changes
Apr 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove always() and the result == 'skipped' conditions from invoke-build-docker.
This is the same issue fixed for invoke-tests-web-console-e2e. The always() condition was added to allow Docker to build even when upstream jobs were "skipped", a scenario that only existed with the artifact-caching feature reverted in #5974. Without that feature, Rust/Java builds are never legitimately skipped, so always() causes Docker to keep running when the workflow is cancelled (upstream jobs get cancelled → skipped → Docker condition evaluates true).
Removing the if: entirely means Docker only builds when all upstream jobs actually succeed, and aborts with the rest of the workflow on cancellation.