Need advice about which tool to choose?Ask the StackShare community!
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.
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
I think I've tried most of the CI tools out there at some point. It took me a while to get around to Buildkite because at first I didn't see much point given it seemed like you had to run the agent yourself. Eventually it dawned on me why this approach was more ingenious than I realised:
Running my app in a production (or production-like) environment was already a solved problem, because everything was already in some form of "everything as code". Having a test environment where the only difference was adding the Buildkite agent was a trivial addition.
It means that dev/test/prod parity is simple to achieve and maintain. It's also proven to be much easier to support than trying to deal with the problems that come with trying to force an app to fit into the nuances and constraints that are imposed by the containers/runtime of a CI service. When you completely control all of the environment the tests are running in you define those constraints too. It's been a great balance between a managed service and the flexibility of running it yourself.
And while none of my needs have hit the scale of Shopify (I saw one of their engineers speak about it at a conference once, I can't find the video now though ๐) it's good to know I can scale out my worker nodes to hundreds of thousands of workers to reduce the time it takes for my tests to run.
I would recommend you to consider the JFrog Platform that includes JFrog Pipelines - it will allow you to manage the full artifact life cycle for your sbt, docker and other technologies, and automate all of your CI and CD using cloud native declarative yaml pipelines. Will integrate smoothly with all your other toolset.
more configurable to setup ci/cd: * It can provide caching when build sbt, just add this section to yml file * Easy to use, many documentation
Weakness: * Need use gitlab as repository to bring more powerful configuration
Pros of Buildbot
- Highly configurable builds9
- Hosted internally5
- Beautiful waterfall5
- Free open source4
- Python3
- No external web fonts by default1
Pros of Jenkins X
- Kubernetes integration7
- Scripted Pipelines5
- GitOps4
Sign up to add or upvote prosMake informed product decisions
Cons of Buildbot
Cons of Jenkins X
- Complexity1
