When comparing Hudson vs Buildkite, the Slant community recommends Buildkite for most people. In the question“What are the best continuous integration tools?” Buildkite is ranked 23rd while Hudson is ranked 27th. The most important reason people chose Buildkite is:
The web UI allows writing a build script inline, running a script from your repository, or creating a whole pipeline. Docker support is built-in.
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 Very easy to set up
The web UI allows writing a build script inline, running a script from your repository, or creating a whole pipeline. Docker support is built-in.
Pro Allows parallel jobs
Buildkite allows you to configure your build in order to run parallel jobs and obtain considerably faster results.
Pro Scheduled builds
Run builds on a cron-like schedule to rebuild a master branch or run an import process.
Pro Run your own build servers
Run an agent on your own servers (AWS, etc) so that you have control over what your builds can access.
Pro Intergrates with VCS
Integrates with GitHub, GitHub Enterprise, Bitbucket, Bitbucket Server, GitLab, Codebase, or any custom Git repository.
Pro Affordable
One plan that gives you everything at a reasonable price.
Pro Plugin support for docker and docker-compose
Pro Concurrency control
Make sure only one deploy build runs at a time with concurrency control.
Pro Config driven build process
While you can define your build process in the dashboard, you can also run it from config files in the repository.
Pro Responsive support
Support respond quickly and listen to feedback.
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.