ci: key main-push concurrency group on SHA to stop run eviction#1124
Merged
Conversation
Pushes to main all shared one concurrency group keyed on github.ref (the literal refs/heads/main), so a tightly-clustered merge cadence evicted previously-queued CI runs, surfacing as red cancelled runs. Key the push path on github.sha so no main run evicts another; PRs keep per-ref grouping plus cancel-on-new-push. Co-authored-by: Will Pfleger <pfleger.will@gmail.com> Signed-off-by: Will Pfleger <pfleger.will@gmail.com>
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
1 participant
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.
Pushes to
mainall shared one concurrency group keyed ongithub.ref— the literal stringrefs/heads/mainfor every push. Under a tightly-clustered merge cadence, each new push entered the shared group and evicted the previously-queued CI run, surfacing as redcancelledruns (the "27/29 succeeded" pattern), not real test failures.Keys the push path on
github.shaso each main push gets its own group and no run ever evicts another. PRs are unchanged: thepull_requestbranch of the ternary keepsgithub.ref(refs/pull/<n>/merge), preserving per-PR grouping pluscancel-in-progress: truecancel-on-new-push.cancel-in-progressis untouched. Sprig/Docker have no concurrency block and are unaffected.