Are there real tangible differences or is it just a matter of taste?
真的有实际差异还是只是品味问题?
9 个解决方案
#1
20
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.
获得巡航控制设置和维护比TeamCity花费更多时间(您可以在几分钟内设置自动化项目(sln)构建)。 TeamCity还有一些非常好的功能,例如立即报告构建失败(通过电子邮件,jabber,网站),因此您不必等待x分钟。
Version 4 (currently EAP) also has a feature that runs failed tests first, so you know if you fixed the build quickly.
版本4(当前为EAP)还具有首先运行失败测试的功能,因此您知道是否快速修复了构建。
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.
所以...我的投票支持团队城市,除非你的团队如此之大,你必须付钱......在这种情况下,我不知道。
#2
9
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.
TeamCity网站上的TeamCity与CruiseControl和CruiseControl.NET进行了比较,网址为http://www.jetbrains.com/teamcity/documentation/featureMatrix.html。显然有点倾向于支持TeamCity,但认为它可能会有所帮助。
For me, I had to go with CruiseControl.NET because it supports SourceGear Vault and TeamCity does not.
对我来说,我不得不使用CruiseControl.NET,因为它支持SourceGear Vault,而TeamCity则不支持。
#3
4
TeamCity is very easy too use and maintain. If you are starting new then use TeamCity.
TeamCity非常容易使用和维护。如果您要开始新的,请使用TeamCity。
#4
3
TeamCity's pre-tested or delayed commit can be a nice feature depending on your specific needs.
TeamCity的预测试或延迟提交可能是一个很好的功能,具体取决于您的具体需求。
#5
3
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.
我个人在CC.NET上,因为我可以自定义它,我们将它用于各种各样的事情,比如运行Red Stone的EggPlant,生成本地化报告,在许多不同的框架和3 OS上运行UnitTests使用MONO。我真的觉得设置很简单,只需要在不到5分钟的时间内完成一个简单的单一解决方案的编译。但是,我已经检查了Team City,它看起来很酷,我只需要能够自定义。
#6
1
Personal choice, but TeamCity is very pleasant to install and to look at.
个人选择,但TeamCity非常适合安装和查看。
#7
1
Team city doesn't have PHP support so its not interesting for me. I think this is a personal choice.
团队城市没有PHP支持,所以它对我来说不是很有趣。我认为这是个人选择。
#9
0
TeamCity can have PHP support, check the URL below:
TeamCity可以获得PHP支持,请查看以下URL:
#1
20
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.
获得巡航控制设置和维护比TeamCity花费更多时间(您可以在几分钟内设置自动化项目(sln)构建)。 TeamCity还有一些非常好的功能,例如立即报告构建失败(通过电子邮件,jabber,网站),因此您不必等待x分钟。
Version 4 (currently EAP) also has a feature that runs failed tests first, so you know if you fixed the build quickly.
版本4(当前为EAP)还具有首先运行失败测试的功能,因此您知道是否快速修复了构建。
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.
所以...我的投票支持团队城市,除非你的团队如此之大,你必须付钱......在这种情况下,我不知道。
#2
9
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.
TeamCity网站上的TeamCity与CruiseControl和CruiseControl.NET进行了比较,网址为http://www.jetbrains.com/teamcity/documentation/featureMatrix.html。显然有点倾向于支持TeamCity,但认为它可能会有所帮助。
For me, I had to go with CruiseControl.NET because it supports SourceGear Vault and TeamCity does not.
对我来说,我不得不使用CruiseControl.NET,因为它支持SourceGear Vault,而TeamCity则不支持。
#3
4
TeamCity is very easy too use and maintain. If you are starting new then use TeamCity.
TeamCity非常容易使用和维护。如果您要开始新的,请使用TeamCity。
#4
3
TeamCity's pre-tested or delayed commit can be a nice feature depending on your specific needs.
TeamCity的预测试或延迟提交可能是一个很好的功能,具体取决于您的具体需求。
#5
3
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.
我个人在CC.NET上,因为我可以自定义它,我们将它用于各种各样的事情,比如运行Red Stone的EggPlant,生成本地化报告,在许多不同的框架和3 OS上运行UnitTests使用MONO。我真的觉得设置很简单,只需要在不到5分钟的时间内完成一个简单的单一解决方案的编译。但是,我已经检查了Team City,它看起来很酷,我只需要能够自定义。
#6
1
Personal choice, but TeamCity is very pleasant to install and to look at.
个人选择,但TeamCity非常适合安装和查看。
#7
1
Team city doesn't have PHP support so its not interesting for me. I think this is a personal choice.
团队城市没有PHP支持,所以它对我来说不是很有趣。我认为这是个人选择。
#8
#9
0
TeamCity can have PHP support, check the URL below:
TeamCity可以获得PHP支持,请查看以下URL: