Continuous Integration - with what to start: CruiseControl.NET vs TeamCity vs Visual Studio Team System -
i'm new continuous integration. want advice tool should start deal with. see biggest tools right now: cruisecontrol.net, teamcity , visual studio team system.
i'm using tools: visual studio 2010, mercurial, nant, nunit.
both teamcity , cruisecontrol.net work fine set of tools. can consider alternatives :
- hudson (free, ui-based setup)
- visual studio team system (expensive (about 6000$), ui-based setup)
- cruisecontrol.net (free, xml-based setup)
- teamcity (professional edition of teamcity free, ui-based setup)
the difference :
1) pricing. cruisecontrol.net , hudson free , open source, while visual studio team system , teamcity cost money (however professional edition of teamcity free).
2) set process. systems have pretty simple ui continuous integration processes except cruise control .net - uses xml-based configuration files instead (example)
essentially need integration system run nant script on commit event , show report. every continuous integration system can this. recommend hudson because is:
- free
- easy set up
Comments
Post a Comment