Azure DevOps Release Pipeline: Apparent contradiction between Releases tab and Deployments tab as to which is the current release
We have a release pipeline with several stages. I'm trying to determine what the release is that's currently deployed to the UAT stage. It seems that the Releases tab and the Deployments tab for the release pipeline show different releases as the one currently deployed to UAT. Which is correct?
Here is the Releases tab, filtered to show the currently deployed releases. It seems to indicate release 6.0.3571.0.01 is the current release in UAT:
Here is the Deployments tab, filtered to show only UAT. It seems to show release 6.0.3582.0.01 is the most recent release deployed to UAT:
Which is the actual release in UAT, 6.0.3571.0.01 or 6.0.3582.0.01?
Normally, the Currently deployed for each stage is based on the latest run of each stage.
For example, release-1 triggered before release-2, but the UAT stage of release-1 runs after that of release-2, at this time, the Currently deployed for UAT stage is marked on release-1 rather than release-2.
On the Deployments tab, it just lists all the existing deployments on all stages or the specified stage by filter.
For your case, if you have checks (Pre-deployment approvals or Gates) set on the UAT stage, when the checks of UAT stage of release 6.0.3582.0.01 got passed before that of release 6.0.3571.0.01, the UAT stage of release 6.0.3582.0.01 would run before that of 6.0.3571.0.01. So, the deployment of UAT stage in release 6.0.3571.0.01 will be considered as the latest deployment (currently deployed) for UAT stage.
Similarly, if you manually start the UAT stage of release 6.0.3582.0.01 before that of release 6.0.3571.0.01, the deployment of UAT stage in release 6.0.3571.0.01 also will be considered as the latest deployment (currently deployed) for UAT stage.
- How do I provide service principal's authorization for an API call in a DevOps pipeline
- Azure DevOps Release Pipeline: Apparent contradiction between Releases tab and Deployments tab as to which is the current release
- Release Pipeline throws the following error: Unable to apply transformation for the given package - Changes are already present in the package
- Azure Devops pipeline schedule releases old releases
- Which scope takes precedence in an release pipeline variable?
- How to add tag to a build from classic release after successful deployment to stage
- Powershell: Can't update a registry path because it doesn't exist (but it actually exists)
- Use git tag or package.json version as Release name in VSTS
- How can i get the Options>Integrations configuration parameters from my projects
- How to schedule the release trigger for every 15 days in Azure devops release pipeline
- Azure Devops 'git' is not recognized as an internal or external command on my Release pipeline
- Azure devops pipeline - Specific verion for Sqlpackage
- Using Azure Devops deploy release to multiple repos
- Azure DevOps REST API - Update pre-deployment artifacts
- Duplicate a VS Web Deploy Publish (.pubxml) in Azure DevOps
- Azure DevOps releases - how to properly perform a release pipeline (Linux)
- start-process : The input object cannot be bound to any parameters for the command
- Azure Devops - How to pass database connection string as environment variable dynamically (azure cli)
- Azure CICD pipelines
- Approval on azure release pipeline - on task level
- how to verify if other build has been built successfully before deploying the release in azure devops
- After creating a deployment pipeline specifying the resource name, all existing pipelines now require permission to deploy
- Creating an Azure DevOps release pipeline using YAML config only
- Helm vs Replace Tokens in VSTS
- Does Azure DevOps have a way to replace files in a ZIP artifact during release pipe?
- Is it possible to disable manual trigger for release pipeline in azure devops
- Where is azure pipelines tasks logs are getting stored in agent
- Azure pipeline branch name for build and release
- Replace Token task in the Release pipeline does not replace token in file
- How to include Source Branch name or pull request ID in ADO release title?