VSTS: Unable to add Build Tag which trigger release

azure-devops azure-pipelines azure-pipelines-release-pipeline
Stephane picture Stephane · Jun 21, 2017 · Viewed 8.6k times · Source

In VSTS online, I have in my Release process (Under Triggers) the Continuous Deployment checked. On the Set trigger on artifact source, I put a Tag condition (with tags) set to Automated.

Release trigger

I also have a tag in the Build Process. (Correctly adds the Tag to the build)

But my release is not triggered automatically? In the Deployments status (In my Build) it says "Tags set for release trigger did not match the tags in build branch". But they match (See pictures). What could be the issue?

Build

Answer

Marina Liu picture Marina Liu · Jun 22, 2017

This is because you added the tag Automated after the build is finished (by label source or manually). This can’t trigger CD release. Tags should be add during a build (not a build is finished). So you can add a power shell task with inline script in your build definition:

Write-Host "##vso[build.addbuildtag]Automatd"

Then the release will be trigger after build is finished.

enter image description here

Related questions

Azure DevOps, YAML release pipelines?

I am following this process to create a YAML build pipeline for a .NET Core Web API project: https://docs.microsoft.com/en-us/azure/devops/pipelines/get-started-yaml?view=vsts When it comes to releasing it, I note that the (recently …

Read More
Azure DevOps pipeline release Error: No package found with specified pattern: D:\a\r1\a\**\*.zip

I have an ASP.NET Core project in Azure DevOps repository and it gets built OK using the DevOps build pipeline. However, the release over that builds always fails with this error: Error: No package found with specified pattern: D:\…

Read More
How to publish artifacts separately for each project in solution from VSTS CI pipeline?

In my solution, I have two projects (a Asp.net MVC and a Windows Service). I want to create CI/CD pipeline to deploy web application and windows service on different VMs. But to achieve this my CI pipeline should …

Read More