CruiseControl .NET - 配置哪些内容以避免多次触发 CI 构建
我希望为我的开发安装基于 CuriseControl .NET 的 CI 流程 - 一个由 15 名开发人员组成的小团队，在一个解决方案中同时处理多个项目。
现在我的问题是我需要配置什么以避免触发任何潜在的多个并发 CI 构建。 我可能会在这里问一个愚蠢的问题，但无论如何，问总比陷入麻烦好:-)
假设我已将 CC 配置为每 2 分钟检查一次源修改。 如果一名开发人员在 10.00 集成某些内容，CC 将在 10.02 识别该内容并开始提取源代码并开始构建、运行 tets 等。
同时，如果另一位开发人员在 10.03 签入某些内容，CC 是否会在 10.05 再次触发再次拉取源代码并开始构建 - 虽然它已经在之前的基础上构建了？
由于构建文件夹在每种情况下都是相同的，所以这不是问题吗？
或者 CC 是否知道它已经在构建它，因此它不会触发另一个构建激活（基于第二个开发人员的第二次签入）？
请帮忙。
I want got CuriseControl .NET based CI process installed for my development - a small team of 15 developers, concurrently working on several projects in one solution.
Now my question is what do i need to configure so as to avoid any potential multiple concurrent CI builds getting triggered. I amy be asking a stupid question here, but nevertheless better to ask than end up in trouble :-)
Lets say i have configured the CC to check for source modifications every 2 minutes.
If one developer integrates something at 10.00 the CC will recognise that at 10.02 and start to pull source and start building, running tets etc.
In the meanwhile, if another developer checks-in something at 10.03, would the CC get triggerd again at 10.05 to pull source again and start building - while its already building on the earlier one?
Since the build folder will be same in each case, would it not be a problem.
Or would the CC know that its alraedy building it, so it will not trigger another build activation (based on teh second check-in by th second developer)?
Please help.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Cruise-control 在构建项目时不会检查该项目的修改情况。
要对此类事情进行更多控制，请查看集成队列。
Cruise-control will not check for modifications to a project while it's already building said project.
For more control over that sort of thing, check out integration queues.