When comparing Hudson 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 Hudson is ranked 27th. 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 Most of the features found on Jenkins are also available for Hudson
Since Jenkins and Hudson share much of the same code base, they also share many of the same features. Hudson is also very easy to install: there is simply a single .war file which is run inside the root of the directory where Hudson will be installed.
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 Superseded by Jenkins
Jenkins is a fork from Hudson and therefore inherits most of it's source code. But Jenkins has far more commits and is a lot more active on the development side than Hudson. A lot of plugin developers have also chosen to support Jenkins and develop their product for Jenkins only.
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.