Block release on non-green CI - #8
Merged
Merged
Conversation
No override flag - a release requires a green run on the packaging tip. An unreachable API blocks too: releasing blind is the same risk as releasing red. Dry runs report and continue. Signed-off-by: Danius Kalvaitis <danius@kurokesu.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.
Summary
release.shrefuse to tag unless the latest CI run on thepackaging tip is green.
Test plan
./release.sh --dry-runwith CI green: silent pass../release.shwhile post-merge CI is in progress: ERROR, exit 1.