How to make TeamCity stop checking for changes and start building!

I had a delicate issue on the new server. Builds would work for any given period of time and then I got a message about java jada jada jada time out. As it turns out there is a bug with the jgit library that TeamCity uses and unfortunately Jetbrains does not have rights or something to modify this by themselves since it’s a third party library. The strange thing is that it was never a problem on my machine but on the server it turned out to cause problems.

A quick search actually brought me straight to the solution. The information is contained within a YouTRACK issue http://youtrack.jetbrains.net/issue/TW-9574 but I’ll summarize it here in brevity.

1. Inside the .BuildServer/config directory create a new file called internal.properties
2. Copy the contents from my internal.properties at the bottom
3. Download jetbrains.git.zip
4. Stop TeamCity
5. Delete the .BuildServer\plugins\jetbrains.git folder
6. Delete the .BuildServer\plugins\jetbrains.git.zip file
7. Copy the new jetbrains.git.zip to .BuildServer\plugins\
8. Start TeamCity

teamcity.git.fetch.separate.process=true
teamcity.git.fetch.timeout=0
teamcity.git.clone.timeout=0

That’s it, TeamCity should start checking for changes again. If not I recommend contacting Jetbrains about it.

-Have fun