Cruise vs. TeamCity vs. CruiseControl.net

Question

We use CruiseControl.net, and we look at the transition to the city of the team, but I just noticed that thinkworks has another product called Cruise

http://studios.thoughtworks.com/cruise-continuous-integration

Does anyone use this product in a production environment, and if so, they have an opinion on this product compared to the city of the team.

Answer 1

We use TeamCity in our company, and we are very pleased with this. It is easy to configure, has a clean interface, and is fairly easy to manage. In addition, VS-Addin is quiet. Only "Auto-commit after successful build" does not work correctly.

I also used CC.Net, but it was missing - simple configuration - authentication - clean ui

Maybe Bassoo atlassians is another possible CI server. Check this.

Answer 2

I worked in a team where we used Cruise, and my story was with CruiseControl.NET.

Functionality is wise. I could not see that there is a big difference between the two, but Cruise has a significantly more “polished” user interface and use prospects.

The cruise seemed to hold your hand in some configuration details, the growth potential, I think, is a standardized approach in all projects. However, I felt that some of these manual ones made you configure your project a little around the product. I am always skeptical about this.

Only my two cents compare Cruise / CruiseControl.NET.

Hope this was helpful.

Answer 3

Also see this SO question: CruiseControl [.Net] vs TeamCity for continuous integration?