VSTS GitVersion variables are not resolved when tagging sources

[BiribiriJaNai]

Using the GitVersion task from VSTS Marketplace, it's working fine updating assembly info and nuget version, but when I want to use any GitVersion variable to tag or label my sources, the variable is not expanded.

and so here is the result in the log file

If I use a user-defined variable in the build process, i.e. $(tagVersion) and assigning a value (1.2.3.4) then the tag is correctly labeled with the variable's value.

[dpurge]

https://connect.microsoft.com/VisualStudio/feedback/details/2743528/invalid-source-label-format-when-labeling-sources-on-successful-build

I think this is not GitVersion issue, but TFS not making variables created by task running on the build agent available on the server where the tag in the source control is created. Such variables are only available for other tasks in the same build (but not even for the very task that is creating the variable)

User-defined variable is created on the server and passed in the context to the build on the agent; this is not the same scenario that GitVersion is in.

I hope this will be fixed eventually.

I cannot test it now, but I think as a workaround you could set the build number format to the NugetVersion variable (GitVersion should update build number) and then use $(Build.BuildNumber) in the tag format.

[BiribiriJaNai]

@dpurge thanks for the workaround!
Indeed, GitVersion already updates the $(Build.BuildNumber) variable, and using it, as is, for tagging works like a charm.
Now I just have to set this variable to the Nuget version.

[bastianjohn]

I have a similar problem. I want to use the $(GitVersion_FullSemVer) for the Build number format but also want to pass the $(GitVersion_AssemblySemVer) to another VSTS Task (see the screenshot).
The BuildNumber will be correctly replaced, but all variables with $(GitVersion are not working and will be displayed as "$(GitVersion_AssemblySemVer)" instead of i.e. "1.0.0.0".

Do you have any idea?
Thanks!

ps: Great VSTS Task! Thanks!

[pascalberger]

@bastianjohn VSTS variables created by GitVersion are in the form GitVersion.* not GitVersion_*. See documentation.

[pascalberger]

As @dpurge mentioned this is not an issue with GitVersion but with how variables are scoped on VSTS. Setting of build number is handled specially by GitVersion by using the appropriate service message.

Closing this since I don't see anything which we can do here from GitVersion side.