Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Cruise Control vs GoCD, the Slant community recommends GoCD for most people. In the question“What are the best continuous integration tools?” GoCD is ranked 18th while Cruise Control is ranked 33rd. The most important reason people chose GoCD is:
GoCD supports pipelines natively. This way you can build your projects by pipelining them.
Specs
Question Ranking
Pros
Pro .NET version
Cruise Control .NET can be used on Windows to build .NET applications, although it is dated by now, it still can be interesting for use on low-spec systems.
https://sourceforge.net/projects/ccnet/
Pro Free and open source
Cruise Control is a free and open source project built with Java and hosted on Sourceforge.
Pro Native support for pipelines
GoCD supports pipelines natively. This way you can build your projects by pipelining them.
Pro Good traceability of what contributed to a given artifact
GoCD's LEAN value stream UI helps all stakeholders focus on efficient product delivery (instead of collections of technical tasks).
Cons
Con A bit tricky to set up
CruiseControl may be a bit tricky to set up. However, it has been around for quite a while so it should be pretty easy to find resources to help you out.
Con Need Scripts for everything
Almost all operations are shell based, they are not configurations possible, your CI is as good as your scripting
Con Does not offer many plugins
Since it's relatively new and not very popular, there are few plugins available in GoCD.
Con Somewhat tricky to setup
