Azure DevOps multi-stage pipeline deployment to specific environment

Question

We've prototyped a multi-stage YAML pipeline in Azure DevOps. One thing that we need is the ability to manually deploy to one of several environments directly.

In other words, we may want to deploy to Dev environment or to Test environment.

I can think of ways to do it that seem like kludges but would prefer something more proper.

What is the preferred way to set this up?

Does this answer your question? [Manual Trigger on Azure Pipelines Stages (YAML)](https://stackoverflow.com/questions/58667596/manual-trigger-on-azure-pipelines-stages-yaml) check my answer there. — Shayki Abramczyk, Aug 03 '20 at 14:53

score 1 · Answer 1 · answered Aug 03 '20 at 18:50

1

What I would recommend is setting up one pipeline that will accept an environment variable at runtime.

I would strongly recommend against doing this though as it defeats the purpose of CI/CD across environment scopes.

Rather would encourage a multi-stage pipeline with a gate approval to subsequent environments.

The reason being is a singular pipeline is best practice to ensure same code is being deployed to each stage.

answered Aug 03 '20 at 18:50

DreadedFrost

2,602
1
11
29

I agree. I decided not to dig into that in the question, but yes, your suggestion is where we're heading. – GaTechThomas Aug 04 '20 at 22:37
Er, meand 'mix", not "dig". – GaTechThomas Sep 04 '20 at 13:33

score 1 · Accepted Answer · answered Aug 04 '20 at 03:24

Feature "Manually trigger stage(s) in YAML multi-stage pipelines" has been on Roadmap, check the link below:

https://developercommunity.visualstudio.com/idea/697467/manually-triggered-stages-in-yaml-multi-stage-pipe.html

Currently, you can start a manual run and skip the stages you don't want to run in your pipeline. The run pipeline panel presents a list of stages from the YAML file, and you have the option to skip one or more of those stages.

Azure DevOps multi-stage pipeline deployment to specific environment

2 Answers2

Linked