In Azure DevOps release pipeline how to promote the latest version to a stage to which no releases were promoted for some time?
We use on-prem Azure DevOps Server 2019.
Observe the following release pipeline:
Notice the last stage - prod. No code was released to it for some time, but now I do want to release the latest there. But, right now I am forced to release and immediately cancel all the versions in the middle, because this is seemingly the only way to release the latest.
Is this the only way?
Solution
I know this has been answered but I thought it might be worthwhile to point out that you can actually always ensure that you only promote the latest release by ensuring that the Deploy latest and cancel others located on the deployment queue settings section of your pipeline is checked/selected on your prod release stage
- UsePythonVersion0 error in self hosted runner on windows
- In Azure DevOps, how can I define a default template for a field of a work item?
- Child process of an Azure DevOps task is killed when the job stops
- How to replace mermaid diagrams with images, keeping them in markdown format to provide easy preview in TFS/Azure DevOps Server?
- How to import a zscaler certificate into Git
- How to change PR merge commit message?
- Why does DotNetCoreCLI@2 task publish (zip) my API web project instead of my Azure Function?
- Get the commits associated with an Azure DevOps release based on previous release
- Azure Board query to list hours consumed by day between tasks
- Entra Role - Azure DevOps Administrator
- Move workdir to another drive and set max size
- DevOps YAML Pipeline deployment fails when the VSBuild@1 task is put into deployment job
- The app build failed to produce artifact folder Angular Azure Static Web App Deployment Issue
- Get commits of an item in one branch with TFS REST API
- In Azure DevOps release pipeline how to promote the latest version to a stage to which no releases were promoted for some time?
- Get Azure DevOps Teams using .Net Client SDK
- Azure DevOps Pipeline Settings Error - "This setting cannot be changed as it is enforced at the organization level"
- ARM parameters JSON array rendered as string in Azure DevOps pipeline, “Expected double‑quoted property name” error
- Azure Pipeline to trigger Pipeline using YAML
- How to update parameters.json file in logic app standard
- How to run a bash script with arguments in azure devops pipeline?
- Azure DevOps Pipelines: Create a text file with the current build number
- Invoke-Sqlcmd with AAD authentication
- Has there been a recent change to Invoke-Sqlcmd that break it, and if so what's the fix?
- VSTS add argument to dotnet pack command
- How to compare many commits in the same branch between specific commit and current HEAD version in Azure Devops Repos ui
- Setting YAML variables depending on trigger branch
- Issue Referencing Secret Variable in Azure Dev Ops
- How to use matrix variable within pool demands?
- Deployment pipeline for SQL Server 2022 DACPAC file throws an error Microsoft.Data.Tools.Schema.Sql.Sql160DatabaseSchemaProvider is not valid