When comparing Buildkite vs Jenkins, the Slant community recommends Jenkins for most people. In the question“What are the best continuous integration tools?” Jenkins is ranked 3rd while Buildkite is ranked 20th. The most important reason people chose Jenkins is:
Jenkins is a free and open source continuous integration tool, while its source code is hosted on [GitHub](https://github.com/jenkinsci/jenkins/).
Ranked in these QuestionsQuestion Ranking
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.
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.
Pro Free and open source
Jenkins is a free and open source continuous integration tool, while its source code is hosted on GitHub.
Pro Safe to store key environment variables
Self-hosting provides a safe location to store key environment variables since it is the user who is in charge of the server and environment where Jenkins is hosted.
Pro Highly customizable
Even though Jenkins is pretty functional and useful out of the box, there's a large plugin ecosystem from which the user can choose plugins to integrate into their Jenkins build. This is needed for when the user wants to extend any of the tool's features.
Pro Multiple version control systems supported
Supports the most popular version control systems out of the box: SVN, Mercurial, and Git.
Pro A lot of resources and tutorials available
Jenkins has been in development since 2004 and is one of the most popular tools of its kind. This means that its technology is very mature and there is a lot of documentation and resources available for it.
The distributed builds in Jenkins work effectively, thanks to the Master and Slave capabilities.
Pro User can source control their chain of automation
Starting with Jenkins 2.0, the pipeline capability, which has been available as a plugin before this version, has been built into Jenkins itself. This allows developers to describe their chain of automation in text form, which can be version controlled and put alongside the source tree.
Pro Cross-platform build support
Being a Java application it can be installed under any OS: Windows, Linux, and macOS. On the other hand, JNLP slaves also enriches the cross-platform build support for its agents.
Pro Quantity of available Plugins
For most operations we need not reinvent the wheel, there are plugins already existing.
Pro Easy to get up and running
A Jenkins install is very simple and the user can have the service up and running within minutes. To install Jenkins, the command
java -jar jenkins.war is all that is needed - nothing more.
Pro Self hosted
You stay in full control of your source code, build environment and deployment. No third party gets access to your source code or knows exactly how to build your software.
Pro Awards and recognition
Including InfoWorld Bossie Award (Best of Open Source Software Award) in 2011, and Received Geek Choice Award in 2014.
Pro Stable release line for users who want less changes
This is called the Jenkins Long-Term Support (LTS) version and helps to provide the most stable and assuring version of the Jenkins CI possible. Every 3 months, a version (which has been deemed the most reliable by the community) is chosen. After this, its branched, well-tested features are added (if they are missing), it is tested with the new features, bug fixes are then carried out if necessary, and from there it is released as the official Jenkins LTS version.
Pro Encryption of secrets
Thanks to JENKINS Credentials and Plugin.
Pro Multiple test environments for different runtime versions
They can be added easily under your Global Configuration.
Con Poor quality plug-ins that are difficult to combine
There have been several complaints by users regarding the quality of the plug-ins found in Jenkins' official plugin repo. A lot of plugins found in the default plugin directory are no longer actively maintained and as a result, they may be incompatible with later versions of Jenkins or other plugins.
Con High overhead
Unlike some of the simple and hosted alternatives, users need to host and setup Jenkins by themselves. This results in both a high initial setup time, as well as time sunk into maintenance over a project's duration.
Con Unstable and lack of plugin integration QA process
Jenkins without plugins is almost useless. All plugins are treated equal and published almost right away.
Because there is no process for testing Jenkins' integration, the overall Jenkins experience is not that great. Furthermore, Jenkins' core and plugins are released on a regular basis, all requiring instant restarts, meaning that updates appear more than once a day!