CruiseControl [.Net] 与 TeamCity 的持续集成? [英] CruiseControl [.Net] vs TeamCity for continuous integration?
问题描述
根据实际经验，我想问一下您认为哪种自动化构建环境更好.我打算做一些 .Net 和一些 Java 开发，所以我想要一个支持这两个平台的工具.
I would like to ask you which automated build environment you consider better, based on practical experience. I'm planning to do some .Net and some Java development, so I would like to have a tool that supports both these platforms.
我一直在阅读并发现了 CruiseControl.NET，用于 stackoverflow 开发，以及
I've been reading around and found out about CruiseControl.NET, used on stackoverflow development, and TeamCity with its support for build agents on different OS-platforms and based on different programming languages. So, if you have some practical experience on both of those, which one do you prefer and why?
目前，我最感兴趣的是该工具的易用性和管理性，更不用说 CC 是开源的，而且当您有很多项目要运行时，TC 有时会受到许可(因为，我在少量项目中需要它).
Currently, I'm mostly interested in the ease of use and management of the tool, much less in the fact that CC is open source, and TC is a subject to licensing at some point when you have much projects to run (because, I need it for a small amount of projects).
此外，如果有其他工具满足上述要求，并且您认为值得推荐 - 请随时将其纳入讨论.
Also, if there is some other tool that meets the above-mentioned and you believe it's worth a recommendation - feel free to include it in the discussion.
推荐答案
自从推出 Cruise Control(java 版本)以来，我一直在使用持续集成工具.我在某个时候几乎尝试了所有这些.在 TeamCity 中，我从未像现在这样快乐.它的设置非常简单，并且仍然提供强大的功能.显示构建时间、单元测试计数、通过率等的构建统计页面非常好.TeamCity 的项目主页也很有价值.对于简单的 .NET 项目，您只需告诉 TeamCity 解决方案在哪里以及哪些程序集有测试，这就是它所需要的(源代码控制位置除外).我们还使用了一些复杂的 MSBuild 脚本并完成了构建链接.我还完成了两次 TeamCity 升级，而且都很轻松.
I have worked on and with Continuous Integration tools since the one that spawned Cruise Control (java version). I've tried almost all of them at some point. I've never been happier than I am with TeamCity. It is very simple to set up and still provides a great deal of power. The build statistics page that shows build times, unit test count, pass rate etc. is very nice. TeamCity's project home page is also very valuable. For simple .NET projects you can just tell TeamCity where the solution is and what assemblies have tests and that is all it needs (other than source control location). We have also used some complicated MSBuild scripts with it and done build chaining. I have also gone through two TeamCity upgrades and they were painless.
CruiseControl.NET 也运行良好.设置起来比较棘手，但它的历史更长，因此很容易在网上找到解决方案.由于 CruiseControl.NET 是开源的，您还可以选择添加或更改任何您喜欢的内容.自 CruiseControl.NET 发布以来，我一直在使用它，并为 cc.tray 编写了一些早期代码(幸好由更了解的人重新编写).
CruiseControl.NET also works well. It is trickier to set up but it has a longer history so it is easy to find solutions on the web. Since CruiseControl.NET is open source you also have the option of adding or changing whatever you like. I had used CruiseControl.NET since its release and wrote some of the early code for cc.tray (thankfully re-written by someone who knew better).
来自 ThoughtWorks 的 Cruise 看起来也不错，但我认为没有令人信服的理由让我切换.如果我要开始一个新项目，我可能会尝试一下，但 TeamCity 做得很好，让简单的事情变得简单，同时让复杂的事情变得轻松.
Cruise, from ThoughtWorks, also looks quite good but I don't see a compelling reason for me to switch. If I were starting a new project I might give it a try, but TeamCity has done a great job of making the simple things simple while making the complex quite painless.
几周前我们刚刚升级到 TeamCity 5.0，这是另一个无痛升级.它让我们可以利用改进的代码覆盖能力和 GIT 支持.我们现在也在使用已经存在一段时间的个人构建和预测试提交功能.我只是想我应该更新答案以表明 TeamCity 不断改进并且仍然易于使用.
We just upgraded to TeamCity 5.0 a few weeks ago and it was another painless upgrade. It let us take advantage of the improved code coverage capabilities and GIT support. We are also now using the personal build and pre-tested commit features that have been in for a while. I just thought I should update the answer to indicate that TeamCity keeps improving and is still easy to use.
这篇关于CruiseControl [.Net] 与 TeamCity 的持续集成?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
