fix(ci): concurrency group cancels the previous fleet on re-trigger - #3065
Open
gewenyu99 wants to merge 1 commit into
Open
fix(ci): concurrency group cancels the previous fleet on re-trigger#3065gewenyu99 wants to merge 1 commit into
gewenyu99 wants to merge 1 commit into
Conversation
No concurrency existed, so every trigger stacked a new 40-cell fleet beside the old one and mid-flight runs could only be hunted down one by one. Fleets now group by source + wizard/context-mill ref with cancel-in-progress; manual dispatches without refs fall back to the run id and never self-cancel. Generated-By: PostHog Code Task-Id: 2d43c175-646e-4d73-a974-760280c8c95b
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.
wizard-ci had no concurrency config: every trigger (push to a wizard PR, comment, manual dispatch) started a fresh 40-cell fleet next to the running one, and stopping work mid-flight meant finding and cancelling each run by hand.
Adds a workflow-level concurrency group keyed on trigger source + wizard ref + context-mill ref with cancel-in-progress: re-triggering the same ref cancels the previous fleet automatically. Manual dispatches without refs key on the run id, so unrelated runs never cancel each other.
Stopping a fleet by hand stays one command:
gh run list -R PostHog/wizard-workbench -w wizard-ci.yml --status in_progressthengh run cancel <id> -R PostHog/wizard-workbench— cancellation tears down every matrix cell including mid-flight agents.Created with PostHog Code