Team City versus CruiseControl.net- which one is better? [closed]

Question

Are there real tangible differences or is it just a matter of taste?

Answer 1

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.

Answer 2

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.

Answer 3

TeamCity is very easy too use and maintain. If you are starting new then use TeamCity.