teamcity - 应如何在 TeamCity 中为大型存储库配置 Perforce VCS 根？

Question

此问题与 this one 相同，但与 Perforce 而不是 SVN 相关。在 Perforce 中，我们有这些分支:

Development\ProjectA\Trunk 
Development\ProjectA\Release1
Development\ProjectA\Release2

在 TeamCity 中，应该有 3 个独立的 VCS 根，还是 1 个为每个构建指定 check out 规则？

按照链接问题中已接受答案的建议，我更改了我们的设置，让单个 VCS 根包含所有内容。性能很差，初始结账需要 45 分钟。

构建配置设置为结帐服务器端并具有结帐规则，例如:

-:.
+:Development/ProjectA/Trunk 

我担心这个设置不可扩展。如果有 3 个分支需要 45 分钟，那么再发布一些并且结帐时间将令人望而却步。在 TeamCity 中为大型存储库设置 Perforce VCS 根的最佳实践是什么？

Answer 1

联系 Jetbrains 支持后，这就是答案:

The checkout rules are not efficient with Perforce and server-side checkout, we have a separate issue for this performance problem, but I cannot tell you its ID right now. Right now, with server side checkout, TeamCity checks out whole VCS root and after that filters the necessary data according to checkout rules.

The solutions for your problem could be:

• Use checkout on agent. TeamCity perform agent-side checkout efficiently, by creating a dedicated perforce workspace from VCS root configuration and checkout rules.
• use checkout on server, but use dedicated VCS Root configurations.