VSTS build step does not check the build number for environment variables

[roryprimrose]

I have updated my build number configuration in the VSTS build definition to $(GitVersion_NuGetVersionV2) as per the documentation in order to get the build number to match the package version being deployed.

One of my builds had the GitVersion build step included which was being executed before the msbuild step. The issue this caused is that the GitVersion build step assigned the default git version label as the build number rather than first evaluating whether the build number was environment variable which is what GitVersionTask does. As this was set by the GitVersion build step, the environment variable was lost from the build number and then GitVersionTask via msbuild could not assign the correct build number.

[pascalberger]

$(GitVersion_NuGetVersionV2) should work fine for setting the build number if set as the Build number format and a GitVersion VSTS task is added to the build definition.

I don't really get what your exact situation is. Are you using the VSTS GitVersion task or the GitVersion MsBuild task?
Easiest solution would be to use the VSTS GitVersion extension, which should work out of the box. If you're using the GitVersion MSBuild task you'll need to yourself send a service message to VSTS to set the VSTS buildnumber, since the buildnumber will be expanded at the start of the build at which time you don't have the environment variable available.

[asbjornu]

Closing due to inactivity. Reopen whenever new information is available.