TeamCity is checking out the wrong revision from Mercurial

We are having intermittent occurances of TeamCity builds that fail to pull the most recent revision (HEAD) from Mercurial. Deleting the TC's cloned repo, which forces TC to do a fresh checkout, fixes the problem.

What is really strange is that if we login to the TC server and use the Mercurial command line to find the most recent revision in the cloned repo, we find the expected revision which is always a few revs newer than what TC keeps building.

Any ideas what would cause this? This is causing us a lot of headaches since it tends to popup at all the wrong times (i.e. when we are trying to build hotfixes!).

2 comments
Comment actions Permalink

Hi Joshua,

could you please enable debug-vcs loggin preset and provide contents of teamcity-vcs.log for the moment when this problem occurs. Also, what version of TeamCity do you use?

0
Comment actions Permalink

We are running TeamCity 6.5.1. I've enabled the debug-vcs logging that you suggested (thanks!) and will post further when I'm able to collect more details.

0

Please sign in to leave a comment.