Team City 与 CruiseControl.net - 哪一个更好？
是否存在真正明显的差异，或者只是品味问题？
Are there real tangible differences or is it just a matter of taste?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
是否存在真正明显的差异，或者只是品味问题？
Are there real tangible differences or is it just a matter of taste?
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
接受 或继续使用网站，即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论（9）
巡航控制设置和维护比 TeamCity 需要更多时间（在 TeamCity 中您可以在几分钟内设置自动化项目 (sln) 构建）。 TeamCity 还具有一些非常好的功能，例如立即报告构建失败（通过电子邮件、jabber、网站），因此您不必等待 x 分钟。
版本 4（当前为 EAP）还具有首先运行失败测试的功能，以便您知道是否快速修复了构建。
所以...我投票给teamcity，除非你的团队太大了，你必须为此付费...在那种情况下，我不知道。
Getting cruise control setup and maintained takes more time than TeamCity (where you can setup automated project (sln) build in matter of minutes). TeamCity also has a couple of very nice features, such as reporting build failure (via email, jabber, web site) immediately, so you don't have to wait for x minutes.
Version 4 (currently EAP) also has a feature that runs failed tests first, so you know if you fixed the build quickly.
So... my vote goes for teamcity, unless your team is so big you have to pay for it... In that case, I don't know.
TeamCity 网站上有 TeamCity 与 CruiseControl 和 CruiseControl.NET 的比较，网址为 http:// www.jetbrains.com/teamcity/documentation/featureMatrix.html。 显然，它会有点偏向 TeamCity，但我认为无论如何它可能会有所帮助。
对我来说，我必须选择 CruiseControl.NET，因为它支持 SourceGear Vault，而 TeamCity 不支持。
There's a comparison of TeamCity to CruiseControl and CruiseControl.NET on the TeamCity website at http://www.jetbrains.com/teamcity/documentation/featureMatrix.html. It's obviously going to be a bit skewed in favor of TeamCity, but thought it might help anyway.
For me, I had to go with CruiseControl.NET because it supports SourceGear Vault and TeamCity does not.
TeamCity 也非常易于使用和维护。 如果您是新手，请使用 TeamCity。
TeamCity is very easy too use and maintain. If you are starting new then use TeamCity.
TeamCity 的预测试或延迟提交可能是一项不错的功能，具体取决于您的具体需求。
TeamCity's pre-tested or delayed commit can be a nice feature depending on your specific needs.
我个人使用 CC.NET，因为我可以自定义它，我们用它来做各种各样的事情，比如运行 Red Stone 的 EggPlant、生成本地化报告、在许多不同的框架和 3 个操作系统上运行单元测试使用单声道。 我确实发现它很容易设置，只需对单个解决方案进行简单编译即可在不到 5 分钟内完成设置。 然而，我已经查看了 Team City，它看起来很酷，我只需要定制的能力。
I personally am on CC.NET due to the fact that I can customize the heck out of it, we use it for all sorts of things like running Red Stone's EggPlant, Producing Localization Reports, Running UnitTests in many different frameworks and on the 3 OS's using MONO. I really found it easy to set up and was up in less than 5 minutes just doing a simple compile of a single solution. However, I have checked out Team City and it looks cool, I just need the ability to customize.
个人选择，但 TeamCity 的安装和外观都非常令人愉悦。
Personal choice, but TeamCity is very pleasant to install and to look at.
Team city 不支持 PHP，所以我对它不感兴趣。 我认为这是个人选择。
Team city doesn't have PHP support so its not interesting for me. I think this is a personal choice.
Team city 支持 Source Gear
Team city supports Source Gear
TeamCity 可以支持 PHP，请检查以下 URL：
http://www.waltercedric.com/joomla-mainmenu-247/370-continuous-build/1552-configuring-teamcity-maven-for-php -for-joomla-连续-build.html
TeamCity can have PHP support, check the URL below:
http://www.waltercedric.com/joomla-mainmenu-247/370-continuous-build/1552-configuring-teamcity-maven-for-php-for-joomla-continuous-build.html