I am evaluating TeamCity on Windows as a possible candidate for our new continuous integration server. I have a very large Mercurial repo, the repo is about 10G and the source code that comes out is about 2G. Creating an initial clone from the central hg repo on the local network takes 1-3 hours depending on traffic. We can't even clone successfully over https, we use a Windows shared directory to pull and set up our hgrc with entries something like these:
default = \\hgserver.domain.net\repo
default-push = https://hgserver/repo
Getting the first clone and checkout done in TeamCity is proving problematic. Repeated attempts timed out after about an hour. Using this thread as a base: http://devnet.jetbrains.net/message/5218025#5218025
I was able to manually create the repo in the .BuildServer\system\caches\mercurial\hg_-4798151147468214717 directory. Now it's creating the initial patch, not sure if that will succeed or timeout.
So, some questions:
1) Am I going to be able to get this to work or is this hg repo just too large?
2) Is there a series of steps I can perform to get the initial repo, patch, and source checkout done manually without it taking so long in TeamCity?
3) I've seen references to Git timeout variables. What timout variables are avaiable for me to modify in Mercurial and TeamCity?
4) TeamCity puts the repo in one dir, the source files in another, and I see references to temp dirs in the build file. Where can I find a detailed reference of steps and dirs created/used in a build that has an hg pull/update and an MSbuild step?