GitVersion doesn't pick up version tags assigned to the latest commit

[urig]

I've setup GitVersion as a build step in my TeamCity build configuration.

1. Given that the most recent version tag on master is v1.2.3
2. And TeamCity runs a build based on the latest commit on master
3. When I later tag that same commit with a new version tag: v1.2.4
4. Then when I manually run the TeamCity build, GitVersion ignores the new version tag and again outputs the previous version.

UPDATE: I've struck out the bits about "skipping fetching" below for the reason that fetching is no longer skipped in my build and yet the symptoms above still occur.
In the build log I see the following message:

INFO [05/10/16 7:52:05:74] Skipping fetching, if GitVersion does not calculate your version as expected you might need to allow fetching or use dynamic repositories

Why is GitVersion skipping fetching? How can I "allow fetching"?

Note:

• The VCS root is configured to run "automatically on client".
• The GitVersion build step is based on the GitVersion TeamCity meta-runner.
• I get the exact same behavior even when I use dynamic repositories. :(

[asbjornu]

What are the command line arguments passed to GitVersion? And does changing the VCS Root checkout behavior to "Automatically on agent" change anything?

[asbjornu]

And as I wrote on Gitter, in TeamCity, buildServer.PreventFetch() will return true unless the environment variable Git_Branch is defined.

[urig]

Thanks @asbjornu . I have Git_Branch defined in the TeamCity build configuration as an environment variable. (Shows up as env.Git_Branch).
The VCS root checkout behavior is already set to "Automatically on agent". I get errors if I set it to "Automatically on server".
My command line (generated by the meta-runner) is:
gitversion.exe "D:\TeamCity\buildAgent\work\ac267eddc88660a" /url 'https://github.com/TripChamp/middleware.git' /u 'urig' /p '*****' /output 'buildserver' /l 'D:\TeamCity\buildAgent\work\ac267eddc88660a\GitVersion3.log'

[urig]

I've made two gists with the relevant messages from the TC build log =

• One where the version tag on latest commit is not picked up by GitVersion
• And another where it's picked up by GitVersion after another commit is made

[asbjornu]

@urig It would be neat if the https://github.com/TripChamp/middleware.git repository or a variant of it showing the same problems were public, so I could execute the command line you have there locally and do some debugging. Is that a doable proposition at all?

[JakeGinnivan]

Is the sha GitVersion sees correct?

As far as the logs tell it's picking up the correct tags and moving forward.Interesting we are not seeing anything about dynamic repos. Maybe there is a bug with log output with the switch to Core?

[urig]

@asbjornu I'm afraid that wouldn't be possible. I'll see if I can setup a different private repo where I can repro then give you access to that. (Maybe the repo being private is a part of the root cause?)

@JakeGinnivan Yes, GitVersion is seeing the correct SHA but does not see the new tags applied to it. (Until a new commit is added further down master).

[urig]

@asbjornu I've created a new private repo and was able to reproduce there. I've sent you a "collaborator" invite to this repo. Feel free to try it out.

[urig]

I have a suspicion that the origin of this issue might be in the way TeamCity updates the git repo in "" mode.
Below is the log of git commands that TC uses. Might anyone be able to figure out if somehow these fail to get the new tags over to the local repo (on the TC agent) that GitVersion is using?

"revision: 84044ae5256b1a7238feef6fa9d72a69d4582330"
git show-ref
git -c core.askpass=D:\TeamCity\buildAgent\temp\buildTmp\pass2949790385075181105.bat ls-remote origin
git show-ref refs/heads/master
git show-ref refs/heads/master
"Cleaning D:\TeamCity\buildAgent\work\ac267eddc88660a"
"The .git directory is missing in 'D:\TeamCity\buildAgent\work\ac267eddc88660a'. Running 'git init'..."
git init
git remote add origin https://.git
git pack-refs --all
git config core.sparseCheckout false
git show-ref
git -c core.askpass=D:\TeamCity\buildAgent\temp\buildTmp\pass5143212605327899971.bat ls-remote origin
git show-ref refs/remotes/origin/master
git log -n1 --pretty=format:%H%x20%s 84044ae5256b1a7238feef6fa9d72a69d4582330 --
git branch
git reset --hard 84044ae5256b1a7238feef6fa9d72a69d4582330

[asbjornu]

@urig Thanks. How did you reproduce the the problem in the gitversion-bug repository? I.e. which command did you run?

[urig]

@asbjornu Tx. Here's the full command line. Note that it's run by the TeamCity agent:

C:\ProgramData\chocolatey\bin\gitversion.exe "D:\TeamCity\buildAgent\work\f8fcbd6382456458" /output "buildserver" /l "D:\TeamCity\buildAgent\work\f8fcbd6382456458\GitVersion3.log"

[asbjornu]

@urig Are you able to reproduce locally on the command line, or is it only visible within TeamCity?

[urig]

@asbjornu I'm unable to reproduce on the command line because gitversion ignores my dynamic repository command line switches (!). So currently only visible inside TC build log.
I would love to grab 10 mins of your time online to demo these issues, if at all possible :)

[asbjornu]

I see. How about duplicating this test and see if you can reproduce the problem there, somehow? That would be the best demonstration of the problem as well as the easiest way to fix it.