Bazel vs Jenkins: What are the differences?
Developers describe Bazel as "Correct, reproducible, fast builds for everyone". Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google's software, and thus it has been designed to handle build problems present in Google's development environment. On the other hand, Jenkins is detailed as "An extendable open source continuous integration server". In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
Bazel can be classified as a tool in the "Java Build Tools" category, while Jenkins is grouped under "Continuous Integration".
Some of the features offered by Bazel are:
- Multi-language support: Bazel supports Java, Objective-C and C++ out of the box, and can be extended to support arbitrary programming languages.
- High-level build language: Projects are described in the BUILD language, a concise text format that describes a project as sets of small interconnected libraries, binaries and tests. By contrast, with tools like Make you have to describe individual files and compiler invocations.
- Multi-platform support: The same tool and the same BUILD files can be used to build software for different architectures, and even different platforms. At Google, we use Bazel to build both server applications running on systems in our data centers and client apps running on mobile phones.
On the other hand, Jenkins provides the following key features:
- Easy installation
- Easy configuration
- Change set support
"Fast" is the top reason why over 18 developers like Bazel, while over 497 developers mention "Hosted internally" as the leading cause for choosing Jenkins.
Bazel and Jenkins are both open source tools. It seems that Jenkins with 13.2K GitHub stars and 5.43K forks on GitHub has more adoption than Bazel with 12.2K GitHub stars and 2K GitHub forks.
According to the StackShare community, Jenkins has a broader approval, being mentioned in 1753 company stacks & 1479 developers stacks; compared to Bazel, which is listed in 11 company stacks and 7 developer stacks.