Cancel heavy jobs in progress when git.ref is updated #3674
Conversation
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
eljobe
requested changes
Sep 23, 2025
|
cancellation works as expected |
eljobe
approved these changes
Sep 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
For 4 workflows:
CI,CodeQL,Docker build CIandCheck Submodule Pins, if the corresponding git ref is updated we cancel the old runs.Why cancel in general? To save resources and abandon unnecessary computation.
Why these jobs? Each of these jobs takes at least few minutes to run (considered as heavy).
Why is it safe? None of these jobs do any release or a work where cancellation might yield unexpected results. They are purely build/test/read-only jobs.
closes NIT-3843