Buildbot vs Jenkins: What are the differences?
Developers describe Buildbot as "Python-based continuous integration testing framework". BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. 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.
Buildbot and Jenkins belong to "Continuous Integration" category of the tech stack.
Some of the features offered by Buildbot are:
- run builds on a variety of slave platforms
- arbitrary build process: handles projects using C, Python, whatever
- minimal host requirements: Python and Twisted
On the other hand, Jenkins provides the following key features:
- Easy installation
- Easy configuration
- Change set support
"Highly configurable builds" is the top reason why over 8 developers like Buildbot, while over 497 developers mention "Hosted internally" as the leading cause for choosing Jenkins.
Buildbot 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 Buildbot with 3.98K GitHub stars and 1.36K GitHub forks.
According to the StackShare community, Jenkins has a broader approval, being mentioned in 1753 company stacks & 1479 developers stacks; compared to Buildbot, which is listed in 7 company stacks and 6 developer stacks.