StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Integration
  4. Continuous Integration
  5. Buildbot vs Jenkins X

Buildbot vs Jenkins X

OverviewDecisionsComparisonAlternatives

Overview

Buildbot
Buildbot
Stacks73
Followers128
Votes27
GitHub Stars5.4K
Forks1.7K
Jenkins X
Jenkins X
Stacks147
Followers370
Votes16
GitHub Stars4.7K
Forks800

Buildbot vs Jenkins X: What are the differences?

Buildbot: 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; Jenkins X: A CI/CD solution for cloud applications on Kubernetes. Jenkins X is a CI/CD solution for modern cloud applications on Kubernetes.

Buildbot and Jenkins X can be categorized as "Continuous Integration" tools.

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 X provides the following key features:

  • Automated CI and CD - Rather than having to have deep knowledge of the internals of Jenkins Pipeline, Jenkins X will default awesome pipelines for your projects that implements fully CI and CD
  • Environment Promotion via GitOps - Each team gets a set of Environments. Jenkins X then automates the management of the Environments and the Promotion of new versions of Applications between Environments via GitOps
  • Pull Request Preview Environments - Jenkins X automatically spins up Preview Environments for your Pull Requests so you can get fast feedback before changes are merged to master

"Highly configurable builds" is the top reason why over 8 developers like Buildbot, while over 2 developers mention "Kubernetes integration" as the leading cause for choosing Jenkins X.

Buildbot and Jenkins X are both open source tools. Buildbot with 4K GitHub stars and 1.37K forks on GitHub appears to be more popular than Jenkins X with 2.8K GitHub stars and 498 GitHub forks.

Mozilla, Animoto, and Fetch Robotics are some of the popular companies that use Buildbot, whereas Jenkins X is used by letgo, Zetaops, and Proente. Buildbot has a broader approval, being mentioned in 7 company stacks & 6 developers stacks; compared to Jenkins X, which is listed in 3 company stacks and 7 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Buildbot, Jenkins X

Stratos
Stratos

Jan 13, 2020

Needs advice

We are a mid-size startup running Scala apps. Moving from Jenkins/EC2 to Spinnaker/EKS and looking for a tool to cover our CI/CD needs. Our code lives on GitHub, artifacts in nexus, images in ECR.

Drone is out, GitHub actions are being considered along with Circle CI and GitLab CI.

We primarily need:

  • Fast SBT builds (caching)
  • Low maintenance overhead (ideally serverless)
  • Everything as code
  • Ease of use
181k views181k
Comments
Sri Srinivas
Sri Srinivas

Feb 11, 2020

Needs advice

I want to start automatic regressions for nightly builds and also continuous integration builds. The tests I ran are part of my regression suite. And I want to track the results of these tests.

I am able to do this with Jenkins using the Junit plugin. But, I am trying to do the same with Buildbot, and I am not able to get the report of the tests. So, I just want to know is it possible to get the reporting of tests through Buildbot. If yes, could anyone provide some examples

121k views121k
Comments

Detailed Comparison

Buildbot
Buildbot
Jenkins X
Jenkins X

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.

Jenkins X is a CI/CD solution for modern cloud applications on Kubernetes

run builds on a variety of slave platforms;arbitrary build process: handles projects using C, Python, whatever;minimal host requirements: Python and Twisted;slaves can be behind a firewall if they can still do checkout;status delivery through web page, email, IRC, other protocols;track builds in progress, provide estimated completion time;flexible configuration by subclassing generic build process classes;debug tools to force a new build, submit fake Changes, query slave status;released under the GPL
Automated CI and CD - Rather than having to have deep knowledge of the internals of Jenkins Pipeline, Jenkins X will default awesome pipelines for your projects that implements fully CI and CD; Environment Promotion via GitOps - Each team gets a set of Environments. Jenkins X then automates the management of the Environments and the Promotion of new versions of Applications between Environments via GitOps; Pull Request Preview Environments - Jenkins X automatically spins up Preview Environments for your Pull Requests so you can get fast feedback before changes are merged to master; Feedback on Issues and Pull Requests - Jenkins X automatically comments on your Commits, Issues and Pull Requests with feedback as code is ready to be previewed, is promoted to environments or if Pull Requests are generated automatically to upgrade versions
Statistics
GitHub Stars
5.4K
GitHub Stars
4.7K
GitHub Forks
1.7K
GitHub Forks
800
Stacks
73
Stacks
147
Followers
128
Followers
370
Votes
27
Votes
16
Pros & Cons
Pros
  • 9
    Highly configurable builds
  • 5
    Beautiful waterfall
  • 5
    Hosted internally
  • 4
    Free open source
  • 3
    Python
Pros
  • 7
    Kubernetes integration
  • 5
    Scripted Pipelines
  • 4
    GitOps
Cons
  • 1
    Complexity
Integrations
No integrations available
Kubernetes
Kubernetes
macOS
macOS
Linux Mint
Linux Mint
Ubuntu
Ubuntu
Debian
Debian
Fedora
Fedora

What are some alternatives to Buildbot, Jenkins X?

Jenkins

Jenkins

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.

Travis CI

Travis CI

Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.

Codeship

Codeship

Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.

CircleCI

CircleCI

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

TeamCity

TeamCity

TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.

Drone.io

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Buildkite

Buildkite

CI and build automation tool that combines the power of your own build infrastructure with the convenience of a managed, centralized web UI. Used by Shopify, Basecamp, Digital Ocean, Venmo, Cochlear, Bugsnag and more.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana