The Release Orchestrator extension adds a task to easily execute and track progress of multiple release pipelines in Azure DevOps. You can use this task to orchestrate numerous pipelines and deploy microservices components in a specific order.
The Release Orchestrator task performing Azure DevOps release pipeline execution and provides various customization settings.
It uses either integrated (SystemVssConnection) or user-defined personal access token (PAT) Azure DevOps service endpoint to connect to projects' pipelines.
To perform release pipeline orchestration the task requires Azure DevOps service endpoint with specific access to target project' pipelines to be able to create and manage releases.
There are two types of Azure DevOps service endoints supported:
You may need to check and update the following settings in Azure DevOps to utilize full potential of Release Orchestrator.
Service endpoint permissions
In release pipelines security section of Azure DevOps project allow the following access to user account of the service endpoint:
Please refer to Azure DevOps permissions and security roles documentation for more details.
Approval gates configuration
The task can automate release stage pre-deployment approval, in order to configure it you need:
In case service endpoint user is not in the approval list or is not allowed to approve the release, manual approval is required and a warning is displayed in the release pipeline progress.
Please refer to Azure DevOps approvals and gates documentation for more details.
How To Use
You can choose different strategy for orchestrator to perform target release deployment:
By default, new release deployment uses default stage triggers configured in the target pipeline. In order to deploy specific or manual stages, you need to specify target stages using
Deploying latest release requires you to provide target stages for deployment. The target stages will be re-deployed in sequential order, exactly as you specified.
Deploying specific release requires you to provide target stages for deployment. The target stages will be re-deployed in sequential order, exactly as you specified.
For help with Azure DevOps and release pipelines please refer to official documentation.