Mercurial + TeamCity - Recommended Setting

Question

Does anyone have a recommended best practice for setting up TeamCity with Mercurial? We used to use SVN as a source code provider that worked beautifully, but I try my best to make it work properly with Mercurial. I am sure that part of the time is some time to adapt to the new model, but even so ...

The main problem is that TeamCity continues to insist on doing full clean checks on almost every build. This seems to be a random hash change that it uses to determine where it stores the source code (although the configuration is not changed).

Because we use bitbucket to host our Mercurial repositories, a server that drops 150 MB + of source code and dependencies stops our deployment and continuous build processes each time.

I would appreciate any contribution to what we can do wrong here. Thanks.

Answer 1

Make sure that cleaning all files before installing the assembly is not verified?

In addition, which helped my setup, it was to define a check directory in each assembly configuration => Version control parameters (for example, C: \ TCProjects), so all repositories will be unloaded in one directory, and it’s also easier to check that this happens unlike auto-generated hash directories.