In this post, I have tried to bring the various Continuous Integration tools which are available in the industry. Also, below is the link in which all the detailed features of continuous integration tool has been compared. This is a good reference to teams which are planning to choose a CI tool for the development purpose. http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix
An important point while selecting the CI tool is to check if the CI tool supports all the tools related to Continuous Inspection (Static Code related tools, Code Coverage, Design Validation , Architecture validation etc), Continuous Testing ( Functional, Memory leak , volume, stress related test tools), support for the various plugins. This is very important as team can really focus on the core development work rather than focusing on integration of tools to CI which may not be a priority work at the time of core development. With the right tool selection, teams can really improve the productivity.
List of Tools which are available
Bamboo
http://www.atlassian.com/software/bamboo/
CruiseControl
http://confluence.public.thoughtworks.org/display/CCNET/Welcome+to+CruiseControl.NET
LuntBuild
http://luntbuild.javaforge.com/
ParaBuild
http://www.viewtier.com/products/parabuild/index.htm
Sin
http://sin.tigris.org/
TeamCity
http://www.jetbrains.com/teamcity/
Tinderbox
https://developer.mozilla.org/en/Tinderbox
Pulse
http://zutubi.com/products/pulse/
Bitten
http://bitten.edgewall.org/
BuildBot
http://trac.buildbot.net/
Gump
http://gump.apace.com/
BuildForge
http://www-01.ibm.com/software/awdtools/buildforge/enterprise/
References
An important point while selecting the CI tool is to check if the CI tool supports all the tools related to Continuous Inspection (Static Code related tools, Code Coverage, Design Validation , Architecture validation etc), Continuous Testing ( Functional, Memory leak , volume, stress related test tools), support for the various plugins. This is very important as team can really focus on the core development work rather than focusing on integration of tools to CI which may not be a priority work at the time of core development. With the right tool selection, teams can really improve the productivity.
List of Tools which are available
Bamboo
http://www.atlassian.com/software/bamboo/
CruiseControl
http://confluence.public.thoughtworks.org/display/CCNET/Welcome+to+CruiseControl.NET
LuntBuild
http://luntbuild.javaforge.com/
ParaBuild
http://www.viewtier.com/products/parabuild/index.htm
Sin
http://sin.tigris.org/
TeamCity
http://www.jetbrains.com/teamcity/
Tinderbox
https://developer.mozilla.org/en/Tinderbox
Pulse
http://zutubi.com/products/pulse/
Bitten
http://bitten.edgewall.org/
BuildBot
http://trac.buildbot.net/
Gump
http://gump.apace.com/
BuildForge
http://www-01.ibm.com/software/awdtools/buildforge/enterprise/
References
No comments:
Post a Comment