VSTS - Continuous Delivery - Launch trigger does not work with tags

Question

UPDATE 2017/02/28

Tags in release triggers are not source control tags; they are tags that can be generated by your build step. You can mark your assemblies automatically (see below) or manually during assembly, I have not tried this yet.

My assumption about tags was wrong , which makes this question pretty much invalid. However, I will try to see if I can find some workaround for my exact scenario, and then post it here.

Background

I am customizing the CI / CD pipeline using VSTS, and part of our branching strategy is that only tags release/*that are tagged will be deployed to production .

VSTS Continuous Deployment, . , , :

1

, , , , ( ). .

2

, release/* .

3

. , . , .

PS. , git, CI.

PS. release/* ,

Answer 1

/ .

, - myTag, myTag.

, :

• PowerShell (Inline Script: Write-Host "## vso [build.addbuildtag] myTag" )