水银+ TeamCity - 推荐设置
有人有关于使用 Mercurial 设置 TeamCity 的推荐最佳实践吗？我们之前一直使用 SVN 作为我们的源代码控制提供程序，效果非常好，但我正在努力让其与 Mercurial 一样顺利地工作。我确信其中一部分需要一些时间来适应新模型，但即便如此...
主要问题似乎是 TeamCity 一直坚持对几乎每个版本进行完整的干净检查。它似乎正在随机更改用于确定存储源代码位置的哈希值（尽管配置没有更改）。
当我们使用 bitbucket 来托管 Mercurial 存储库时，服务器每次都会下载 150MB 以上的源代码和依赖项，这会导致我们的部署和持续构建过程陷入停顿。
对于我们在这里可能做错的事情提供任何意见，我们将不胜感激。谢谢。
Does anyone have any recommended best practice for setting up TeamCity with Mercurial? We'd previously been using SVN as our source control provider which worked beautifully, but I'm struggling to get this working as smoothly with Mercurial. I'm sure part of it is some time to adjust to the new model, but even so...
The main issue seems to be that TeamCity keeps insisting on doing complete clean checkouts on almost every build. It seems to be randomly changing the hash it uses to determine where it stores the source code (despite the configuration not changing).
As we're using bitbucket to host our Mercurial repositories, the server pulling down 150MB+ of source code and dependencies each time is grinding our deployment and continuous build processes to a halt.
Would appreciate any input on what we might be doing wrong here. Thank you.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您是否确保未选中“构建前清理所有文件”设置？
另外，对我的设置有帮助的是在每个构建配置中定义一个签出目录=>版本控制设置（例如 C:\TCProjects）因此所有存储库都在同一目录中签出，并且与自动生成的哈希目录相比，检查正在发生的情况也更容易。
Have you made sure that Clean all files before build setting is not checked?
Also what helped my setup was to define a checkout directory in each build configuration => Version Control Settings (eg. C:\TCProjects) thus all repos are checked out in the same directory and it is also easier to check what is happening in contrast with the auto-generated hash directories.