\n
Edit for those considering this sort of approach...
\nFiring off multiple pipelines has complications:
\nIf at all possible, change the approach. Not an easy change, as it may necessitate a design change to the system itself.
\n","author":{"@type":"Person","name":"GaTechThomas"},"upvoteCount":0,"answerCount":1,"acceptedAnswer":{"@type":"Answer","text":"You can add Trigger Azure DevOps Pipeline tasks to the pipeline to kick off stages in other pipelines.
\n\n","author":{"@type":"Person","name":"Hugh Lin"},"upvoteCount":1}}}Reputation: 6113
We have a number of Azure Pipeline stages that we need to be able to choose to kick off, say, in the event of a disaster recovery (DR) situation. We currently have a mix of Classic and YAML pipelines, each with a set of stages that include deployment to a given environment.
Would it be straightforward to deploy a particular stage from each pipeline?
I'm picturing something like a new pipeline that has a series of tasks (maybe in separate jobs or stages) that kick off particular stages in other pipelines. Is this straightforward?
Edit for those considering this sort of approach...
Firing off multiple pipelines has complications:
If at all possible, change the approach. Not an easy change, as it may necessitate a design change to the system itself.
Upvotes: 0
Views: 134
Reputation: 19471
You can add Trigger Azure DevOps Pipeline tasks to the pipeline to kick off stages in other pipelines.
Upvotes: 1