[Chore] Make the deployment acceptance gate non-blocking for publishes - #127
Merged
Merged
Conversation
The smoke test has repeatedly blocked develop image publishing (and with it nightly deploys) on gate-side issues rather than candidate defects. Keep the job running so failures stay visible, but let build/publish proceed without it while the smoke test is stabilized. Restore the build dependency once it is reliable.
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
2 participants
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.
Per Matt: the smoke test keeps blocking develop publishes (and nightly deploys) on gate-side issues, so make it non-blocking while it gets stabilized.
buildno longer depends ondeployment-acceptance; publishes and the ops dispatch proceed regardless of the gate's outcome.deployment-acceptancetobuild.needsre-enables gating.Context: #125 fixed the baseline-tooling deadlock, but its own publish run had not yet proven the gate reliable and further merges keep queueing behind it.