Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m new to Continuous Integration. I want an advice with what tool should I start deal with. I see that this is the biggest tools right now: CruiseControl.NET, TeamCity and Visual Studio Team System.
I’m using this tools: Visual Studio 2010, Mercurial, NAnt, NUnit.
Both TeamCity and CruiseControl.NET will work fine for this set of tools. Also you can consider alternatives :
The difference is :
1) Pricing. CruiseControl.NET and Hudson are free and open source, while Visual Studio Team System and TeamCity cost money (However Professional Edition of TeamCity is also free).
2) Set up process. All systems have pretty simple UI to get up continuous integration processes except Cruise Control .NET – it uses XML-based configuration files instead (Example)
Essentially all you need from integration system is just to run nant script on commit event and show report. Every continuous integration system can do this. I would recommend Hudson because it is: