We recently upgradd to TeamCity 4.5.3 and have been loving it. We also installed the latest stable Mercurial Plugin release after moving our project to hg. Our project requires checking out a few different repositories (FOO, FOO2) with a final structure that looks like
TeamCity Mercurial's default checkout behavior seemed to be to check out the repositories in a flat manner, IE: Using a VCS root for FOO and a VCS root for FOO2 in the project configuration yields a working directory
To get our necessary directory structure, I attempted to make a checkout rule for each repo in the formats "+:.=>FOO" and ".=>FOO" as the mercurial plugin page says is supported, but both times ended up with a working directory with the folder "FOO" created, but with nothing inside, and the same flat checkout from before IE:
My understanding of the checkout rules from using the SVN VCS roots was that ".=>FOO" should create folder FOO and move all of the elements for the VCS root into that directory. When we were using SVN I set up the projects in that manner and they worked succesfully. Is this a misunderstanding of what the ".=>FOO" checkout rule is capable of? If so, is there a way to check out each Mercurial repository into its own directory by configuring the vcs settings or the configuration rules?