CODEWITHSUNDEEP
azure-devopsazure-pipelinesazure-pipelines-release-pipelineazure-artifacts
password
password

Reputation: 481

Promote artifact version to single environment using VS Team Services Release Management

In VS Team Services > Releases, I want to 'promote' a specific build/artifact version to a single environment. For example:

Dev     QA     Prod
v223       
v123   v123

I want to promote #123 to Prod, but it looks like the only way to do that is to Create a release to all 3 environments, which will overwrite #223.

enter image description here

Upvotes: 2

Views: 442

Answers (2)

Eddie Chen - MSFT
Eddie Chen - MSFT

Reputation: 29966

There isn't any way to do this for now. You can submit a feature request on VSTS User Voice: http://visualstudio.uservoice.com/forums/330519-team-services/

Upvotes: 2

Daniel Mann
Daniel Mann

Reputation: 59020

You have a release pipeline that goes Dev -> QA -> Prod. You create a release for version #123 and promote it progressively through the stages in your pipeline. Version #223 can be in Dev, and you can still promote the release for build #123 from QA->Production.

Skipping stages and not testing software in lower environments is a huge problem that results in pain and suffering. One of the cornerstones of a stable release process is consistency. There are tons of ways to make your release process both flexible enough to handle the scenario you're describing while still being consistent. Skipping stages isn't it.

If you need to re-release an older build of your software, it should still go through the same pipeline. Just because it's an old build doesn't mean that you don't need to at least do a cursory investigation to make sure it's being deployed correctly.

Will that overwrite the version currently on the lower environments? Depends on how you structure things! For web applications, maybe you make it multi-tenant, so you can have multiple versions running side-by-side on the same machine. Or deploy to IaaS VMs, so you can just provision a new one and leave the currently-running VM alone. Or deploy to Azure PaaS and use different staging slots for different versions.

Upvotes: 1

Related Questions