Cancel stale CI executions when CI is re-triggered in the same branch/PR #21974
Conversation
This file contains 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
hamzaremmal
reviewed
Nov 19, 2024
Gedochao
added
the
stat:needs decision
hamzaremmal
reviewed
Nov 19, 2024
hamzaremmal
removed
the
stat:needs decision
Co-authored-by: Tomasz Godzik <[email protected]>
KacperFKorban
pushed a commit
to dotty-staging/dotty
that referenced
this pull request
Nov 29, 2024
…/PR (scala#21974) Cancels any in-progress runs within the same group identified by workflow name and GH reference (branch or tag) For example it would: - terminate previous PR CI execution after pushing more changes to the same PR branch Co-authored-by: Tomasz Godzik <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Cancels any in-progress runs within the same group identified by workflow name and GH reference (branch or tag)
For example it would:
Motivated by a long CI queue (taking even up to 10h ) and limited amount of self-hosted runners. Currently merging PR to main triggers a new on-push CI run (taking ~1.5h) - merging multiple PR in a row schedules a separate CI run (that is probably never going to be investigated if it fails)
The second empty commit shows how cancelation is done. Previously triggered CI run is cancelled, any enqueued or currently executed jobs are stopped and annotated with message
Canceling since a higher priority waiting request for 'Dotty-refs/pull/21974/merge' exists