Geek Answers Handbook

VSTS Release Management: Branch Filter on Artifact Source

I am using VSTS build to run CI build. This build definition is the same for all my git branches (wizard, development, functions, etc.).

Now I'm trying to implement a deployment pipeline using VSTS release control. I plan to have two different definitions of release. One for function branches and one for more important industries, such as development and development. Defining a release for function branches will be easier.

I think this is pretty simple and ordinary. In fact, this is pretty much what Microsoft describes as a typical use case for release management .

For both of these pipelines, I want to configure them to start automatically using the Continuous Deployment trigger. When I select this trigger, I have to choose the source of the artifact.

Unfortunately, the artifact source accepts all artifacts (regardless of branch) coming from this assembly definition (my CI assembly). Since I use the same CI assembly definition for all my branches, it seems that I cannot configure my two release pipelines in "Continuous Deployment" and still use the same assembly definition as the source of the artifact.

Does anyone know how to use the same assembly definition for multiple release definitions, but only run the release for a specific branch? Does anyone know a branch filtering method when we determine the source of an artifact?

+8
vsts vsts-build ms-release-management
source share
2 answers

Set up deployment of individual branches

  • Go to Release Management in VSTS
  • Go to release definition
  • Go to trigger tabs
  • Add Continuous Deployment Trigger
  • Here you can select a specific branch (for a branch)

Detect trigger trigger

Feature Availability

  • This feature is available in VSTS.
  • The original version of TFS assumes that it will be available in Server 2017.1, but it is still not available in 2018.1.
+5
source share

There is currently no way in VSTS Release Management to perform branch-based conditional deployment.

An alternative would be to create separate BDs for different branches, and then configure them as sources of artifacts for RD.

It will also give users clarity about the artifact on its own behalf.

+2
source share

More articles:


All Articles