Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Cruise Control vs Wercker, the Slant community recommends Wercker for most people. In the question“What are the best continuous integration tools?” Wercker is ranked 8th while Cruise Control is ranked 33rd. The most important reason people chose Wercker is:
Wercker is based on Docker and it allows developers to create their own deployment stacks inside Docker containers. These stacks range from programming languages, to services, and even to notifications.
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 Ability to create and use custom environments
Wercker is based on Docker and it allows developers to create their own deployment stacks inside Docker containers. These stacks range from programming languages, to services, and even to notifications.
Pro Free unlimited number of private repositories CI while in Beta
While in beta, Wercker offers unlimited free public and private repositories.
Pro Social networking elements
Wercker has an activity feed with which different team members can see and follow everything their colleagues have been doing. This gives the tool a certain social network feel, much like GitHub itself.
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.
