Manual Trigger In Multi-Stage YAML Pipeline - Azure DevOps
YAML pipelines in Azure Pipelines is a great functionality, however, at the time of this writing, it lacks some features. One of those is a manual trigger for a stage. Consider this sample use case:
- PR is merged into the main branch.
- Main pipeline is automatically invoked, YAML definition contains DEV, TEST, PROD stages to deploy to corresponding environments.
- We want to deploy to DEV after each commit to master, however, not to TEST, there could be different reasons why we do not want to deploy to TEST right away after each commit.
How to prevent the pipeline from executing TEST stage but be able to trigger it manually?
As a workaround for not running stage automatically, a condition can be added to execute the stage only if the whole pipeline was triggered manually:
condition: eq(variables['Build.Reason'], 'Manual')
- stage: TEST condition: eq(variables['Build.Reason'], 'Manual') jobs: Deploy steps: - script: echo Hello, World! displayName: 'Run a one-line script'
This condition should be added to the TEST stage. Of course, this check can be combined with other checks to form a larger condition. More about
Build.Reason and other predefined variables here.
When new commit is added to the main branch, pipeline is kicked off automatically but stops after DEV stage:
By triggering run manually TEST stage will be executed if selected in “Run pipeline” → “Stages to run”:
Note: To deploy to the TEST stage we need to create a new run manually. We cannot trigger TEST stage from an existing run.
Use environment approvals to require manual input to run a particular stage. Information about environment approvals is here. Downside: stage is shown as pending until someone approves and fails after timeout. I do not prefer to a run to be marked as pending or failed, although everything executed correctly.
Keep two YAML pipelines: one is triggered on every commit to the main branch and includes only Build and TEST, another one is triggered manually and includes all stages, here you can specify stages to run. Downside: maintenance of two pipelines.
Keep two pipelines: YAML + Classic. Set up Classic Web UI Release Pipeline to deploy to higher environments (in our case TEST and PROD). In this approach we keep Build and DEV stages in yaml definition and TEST and PROD in classic release. Classic pipelines documentation. Downside: definition is spread across different places, classic release definition is not in source control.
Always run the pipeline manually, this will allow to select stages to run. To disable trigger set the following setting in your YAML file: