如何在 TeamCity 中重新组合构建？
我们有很多测试。我可以将它们分解，以便在初始编译构建发生后它们在单独的代理上运行，但是有没有办法重新组合这些结果？拥有 8 个都需要绿色的构建配置，这使得很难看出您是否拥有一个 ubergreen 构建。
一旦我们将构建拆分出来，TeamCity 中是否有办法重新组合/加入构建？ TW-9990 可能会有所帮助 - 允许在依赖项中使用 AND。
We have a lot of tests. I can break these up so that they run on seperate agents after an initial compile build happens, but is there a way I can recombine these results? Having 8 build configurations that all need to be green makes it hard to see if you've got one ubergreen build.
Is there a way in TeamCity to recombine / join builds once we've split them out? TW-9990 might help - allowing ANDs in the dependencies.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我们找到了在 TeamCity 5 中肯定有效的答案：
N 次测试仅构建采用compile.zip!** 并复制到编译输出通常所在位置的构建。 （通过模板）
综合完成：
仅使用合适的成功构建
这一切似乎都运行良好，并且整个 shbang 很容易复制到分支等。我非常高兴 - 这对我们来说已经运行了好几个月了。
We found the answer which certainly works from TeamCity 5:
N test only builds that take compile.zip!** and copy to where the compile output would normally be. (via a template)
Consolidated finish:
Only use successful builds from suitable ones
This all seems to work nicely and the whole shbang is easily copied for branches etc. Am very happy - this has worked well for us for many months now.
不知道如何在本地做到这一点。以下是我关于如何尝试解决此类问题的第一个想法：
祝你好运！
No idea how to do that natively. Here's my first thoughts on how I would try and tackle such a thing though:
Good luck!
跳出框框思考，您可能会拥有一个实际上不执行任何操作的整体构建（或使用您的测试构建配置之一作为“主”），并且对每个拆分测试构建都具有快照依赖性。这样，如果其中任何一个失败，“主”将会失败，因为依赖构建失败。
TW-9990 看起来关心的是构建触发而不是依赖关系。
Thinking outside the box you could have an overall build which doesn't really do anything (or use one of your test build configs as your 'master'), with snapshot dependencies on each of your split test builds. That way if any of them fail, the 'master' will fail because one the dependent build failed.
TW-9990 looks to be concerned with build triggering rather than dependencies.