ci: replace release stage with publishing-gate job configuration#17984
Draft
erikayasuda wants to merge 2 commits intomainfrom
Draft
ci: replace release stage with publishing-gate job configuration#17984erikayasuda wants to merge 2 commits intomainfrom
release stage with publishing-gate job configuration#17984erikayasuda wants to merge 2 commits intomainfrom
Conversation
release stage with publishing-gate job configuration
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
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.
Description
Adding the
publishing-gatejob and moving all test jobs as a requirement. This is to replicate the behavior we currently have implemented by having a separatereleasestage.See the one-pipeline.yml for the source of truth for which jobs are gated. As of writing this PR, this is the list of jobs gated on
publishing-gate:.promote-oci-packagepromote-oci-to-stagingpromote-oci-to-prod-betapromote-oci-to-prodpublish-lib-init-pinned-tagsinternal-publish-lib-init-tagspublish_dora_metrics.gradual-rollout-mutable-tags-baserollout-mutable-tags-stagingrollout-mutable-tags-prodTesting
Trigger the publishing-gate flow on a test branch pipeline
Risks
A full release pipeline run needs to be validated on the first release. This could happen on a release candidate to be safe though.
Additional Notes