Difference between Bamboo Vs TeamCity Vs CruiseControl
TEAMCITY

• TC pre-tested commit is good.
• TC integrates to Visual Studio which is our main IDE.
• JetBrains are more focused on supporting .NET builds than Atlassian is, since JetBrains actually has .NET products so they use it internally.
• Support for .Net projects, as well as Java, in the same product (nice if you need it).
• Server-side code coverage analysis (you could get the same results by running EMMA from the Ant build.xml)
• Server-side static code analysis using IDEA inspections (nice but relies on using IDEA for development – Checkstyle and FindBugs could do something similar from Ant).
• Pre-tested commits. Sends your changes to the CI server for building before committing to version control. Your changes are only checked-in if the build succeeds and all tests pass.

BAMBOO

• Bamboo JIRA integration is awesome. I wish TeamCity provides that kind of integration.
• Bamboo on the other hand looks like a great tool too. It has so many plugins (just like JIRA). It looks nice as well. I can live without VSTD integration, but I really wanted pre-tested commit. Just a note: I did create a feature request ticket to Atlassian telling them about TC’s pre-tested commit feature.

CruiseControl

• “CruiseControl is a framework for a continuous build process.”
• “Bamboo is a continuous integration build server that offers heaps of insight on build processes and patterns via solid reporting metrics.”
• “TeamCity is an innovative, IDE independent, integrated team environment targeted for .NET and Java software developers and their managers.”
• “AnthillPro3 is a third generation Build Management Server.”

Links and Reference:
http://blog.chris-read.net/2007/02/21/quick-comparison-of-teamcity-12-bamboo-10-and-cruisecontrol-26/
http://blog.uncommons.org/2006/12/08/teamcity/
http://poorinnerlife.blogspot.com/2007/09/bamboo-disappointment.html

The post Bamboo Vs TeamCity Vs CruiseControl – Continuous Integration Expert Review appeared first on scmGalaxy.