When comparing Cruise Control vs Bitbucket Pipelines, the Slant community recommends Bitbucket Pipelines for most people. In the question“What are the best continuous integration tools?” Bitbucket Pipelines is ranked 22nd while Cruise Control is ranked 33rd. The most important reason people chose Bitbucket Pipelines is:
Eg: ./1.setup.sh 48s ./2.build.sh 56s With this information, it's easy to find out which line of the script is the bottleneck of the build process.
Ranked in these QuestionsQuestion 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 Provides time taken for each step
Eg:
./1.setup.sh 48s
./2.build.sh 56s
With this information, it's easy to find out which line of the script is the bottleneck of the build process.
Pro Great Jira integration
The same company Atlassian built Jira, which provides top-tier integration with Jira.
Pro Combined service: source control and CI
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 Only 50 mins/month free usage
The Free plan only gives you 50 minutes per month to run the build.
Con Sparse documentation and examples
