ci: abort web console e2e job when workflow is cancelled#6012
Merged
jyotshnayaparla-00 merged 1 commit intomainfrom Apr 8, 2026
Merged
ci: abort web console e2e job when workflow is cancelled#6012jyotshnayaparla-00 merged 1 commit intomainfrom
jyotshnayaparla-00 merged 1 commit intomainfrom
Conversation
gz
approved these changes
Apr 8, 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' condition from invoke-tests-web-console-e2e.
Previously, the job had if: always() && (result == 'success' || result == 'skipped'), which was designed to handle the case where Docker build could be legitimately skipped (when artifacts already existed from a prior run). That logic was part of the artifact-caching feature reverted in #5974 .
Without that feature, Docker is never legitimately skipped, it only gets skipped when an upstream job is cancelled.
The always() condition caused e2e tests to keep running even after the workflow was cancelled. Removing the if: entirely means e2e only runs when Docker actually succeeds, and aborts with the rest of the workflow on cancellation.