When comparing Drone.io vs Buildkite, 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 Buildkite is ranked 23rd. 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 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).
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 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.
