What could make gitversion compute a different version on the same branch (local vs build agent repos)

Question

I have a branch that is committed and synced to TFS 2015.

When running a build on the build agent the gitversion command executed computes a different version.

Locally I get 3.11.0 based on tag 3.10.0.202

On the build agent I get 0.1.0

I feel the change may be related to how the clone is done on the build agent. Can anyone suggest if that seems likely and what might be the difference?

N.B.

• The build agent is just a TFS 2015 build agent running on my machine at present.
• Running the command without no fetch gives the same results
• This is the tag
• The wrong version number was on the build server (via TFS build) but I also reproduced it using the command line. I only posted the latter as it gave the results. I can post an example of the TFS build output when I'm next able to log in the server. The repo in the second example (D:) is the one cloned using the TFS build, while the first one (C:) was cloned using VS 2015.

Answer 1

I could reproduce your scenario by creating a Tag to a history of a branch, and running the gitversion command:

Then I committed and pushed this branch to TFS 2015, on build agent machine, I ran the gitversion command:

In order to found out why they were different, I logged into TFS build agent machine and pulled the branch, I found there was no tag on the branch. That's because using sync or push in Visual Studio would not push the tag.

While GitVersion Docs mentions, if a commit is tagged, then GitVersion will always use that version over any calculated versions. This is so if you rebuild a tag then the same version will be produced.

In conclusion, VS doesn't push the Tag cause this difference. To push the Tag, you have to use command git push --tags.