fix(ci): remove dependsOn from manually-triggered Arc prod Stage_1#1716
Open
zanejohnson-azure wants to merge 1 commit into
Open
fix(ci): remove dependsOn from manually-triggered Arc prod Stage_1#1716zanejohnson-azure wants to merge 1 commit into
zanejohnson-azure wants to merge 1 commit into
Conversation
ADO rejects manually-triggered stages that also declare dependsOn (Manually triggered stages cannot have dependencies). Stage_1 already defaults to depending on the preceding Wait_After_Canary stage, so the explicit dependsOn was redundant; trigger: manual preserves the human gate before any prod1/stable push. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
Problem
The merged PR #1715 added
trigger: manualtoStage_1and kept an explicitdependsOn: [Wait_After_Canary]. Azure DevOps rejects this combination at compile time:Fix
Remove the explicit
dependsOnfromStage_1. In ADO, a stage with nodependsOndefaults to depending on the preceding stage in the list — which isWait_After_Canary— so the ordering (Canary → 25h bake → Stage_1) is preserved.trigger: manualstill enforces the human gate before any prod1/stable push.This matches the existing
Stage_Canary_Regionsstage, which is alsotrigger: manualwith nodependsOnand relies on default sequential ordering.Validation
Stage_1→trigger=manual,dependsOn=None.