When comparing Cruise Control vs Drone.io, the Slant community recommends Drone.io for most people. In the question“What are the best continuous integration tools?” Drone.io is ranked 11th while Cruise Control is ranked 33rd. The most important reason people chose Drone.io is:
Drone.io integrates perfectly with GitHub, BitBucket and Google Code.
Specs
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 Integrated with GitHub, BitBucket, and Google Code
Drone.io integrates perfectly with GitHub, BitBucket and Google Code.
Pro Easy self-hosted setup
Drone can be easily set up locally: all that's needed is Docker.
Pro Docker integration simplifies deployment
Drone uses Docker containers to build and test code. Using Docker containers makes it easier for developers to then deploy this code to production.
Pro Gitea support
Supports Gitea (Git server).
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 Does not allow you to configure two projects using the same GitHub repo
Drone.io does not let developers configure two different projects against the same repository. Instead, one must fork that repository into a new one and use that to create a new Drone.io project.