Buildbot vs GitLab CI

Overview

Buildbot

Stacks73

Followers128

Votes27

GitHub Stars5.4K

Forks1.7K

GitLab CI

Stacks2.3K

Followers1.6K

Votes75

GitHub Stars0

Forks0

Buildbot vs GitLab CI: What are the differences?

### Key Differences between Buildbot and GitLab CI

<Write Introduction here>

1. **Integration with Version Control Systems**: Buildbot offers integration with various version control systems like Git, Mercurial, and Subversion, while GitLab CI is tightly integrated with Git repositories, making it seamless for Git-based projects to set up CI/CD pipelines.
2. **User Interface**: Buildbot has a more minimalistic and basic web interface for monitoring builds, whereas GitLab CI provides a modern and feature-rich interface with detailed build logs, pipeline visualization, and easy navigation.
3. **Hosted vs. Self-hosted**: GitLab CI is part of the GitLab platform, which can be self-hosted or used on GitLab's cloud-based service, while Buildbot is primarily self-hosted, requiring users to set up and maintain their own infrastructure.
4. **Third-party Plugin Ecosystem**: Buildbot has a limited number of plugins available compared to GitLab CI, which has a vast ecosystem of community-contributed plugins and integrations with other tools and services.
5. **Scalability and Performance**: GitLab CI is known for its scalability, handling large projects and thousands of builds efficiently, while Buildbot may face challenges in handling huge workloads or scaling to enterprise-level CI/CD requirements.
6. **Built-in Features**: GitLab CI comes with built-in features like container registry, package registry, and Kubernetes integration for seamless deployment, which may need to be separately configured or integrated with Buildbot setups.

In Summary, the key differences between Buildbot and GitLab CI lie in their integration capabilities, user interface, hosting options, plugin ecosystems, scalability, performance, and built-in features.

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)

Manual

Advice on Buildbot, GitLab CI

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

Anonymous

Feb 14, 2020

Decided

Buddy is one of the most easy-to-use tools for CI I ever met. When I needed to set up the pipeline I was really impressed with how easy it is to create it with Buddy with only a few moments. It's literally like:

Add repo
Click - Click - Click
You're done and your app is on prod :D The top feature that I've found is a simple integration with different notification channels - not only Slack (which is the one by default), but Telegram and Discord. The support is also neat - guys respond pretty quickly on even a small issue.

157k views157k

Comments

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	GitLab CI
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.	GitLab offers a continuous integration service. If you add a .gitlab-ci.yml file to the root directory of your repository, and configure your GitLab project to use a Runner, then each merge request or push triggers your CI pipeline.
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	-
Statistics
GitHub Stars 5.4K	GitHub Stars 0
GitHub Forks 1.7K	GitHub Forks 0
Stacks 73	Stacks 2.3K
Followers 128	Followers 1.6K
Votes 27	Votes 75
Pros & Cons
Pros 9 Highly configurable builds 5 Hosted internally 5 Beautiful waterfall 4 Free open source 3 Python	Pros 22 Robust CI with awesome Docker support 13 Simple configuration 9 All in one solution 7 Source Control and CI in one place 5 Integrated with VCS on commit Cons 2 Works best with GitLab repositories
Integrations
No integrations available	GitLab

What are some alternatives to Buildbot, GitLab CI?

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

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 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

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 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 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 is a CI/CD developer automation platform designed for Microservices & Container Architecture.

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 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

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

Buildbot vs GitLab CI: What are the differences?

### Key Differences between Buildbot and GitLab CI

<Write Introduction here>

1. **Integration with Version Control Systems**: Buildbot offers integration with various version control systems like Git, Mercurial, and Subversion, while GitLab CI is tightly integrated with Git repositories, making it seamless for Git-based projects to set up CI/CD pipelines.
2. **User Interface**: Buildbot has a more minimalistic and basic web interface for monitoring builds, whereas GitLab CI provides a modern and feature-rich interface with detailed build logs, pipeline visualization, and easy navigation.
3. **Hosted vs. Self-hosted**: GitLab CI is part of the GitLab platform, which can be self-hosted or used on GitLab's cloud-based service, while Buildbot is primarily self-hosted, requiring users to set up and maintain their own infrastructure.
4. **Third-party Plugin Ecosystem**: Buildbot has a limited number of plugins available compared to GitLab CI, which has a vast ecosystem of community-contributed plugins and integrations with other tools and services.
5. **Scalability and Performance**: GitLab CI is known for its scalability, handling large projects and thousands of builds efficiently, while Buildbot may face challenges in handling huge workloads or scaling to enterprise-level CI/CD requirements.
6. **Built-in Features**: GitLab CI comes with built-in features like container registry, package registry, and Kubernetes integration for seamless deployment, which may need to be separately configured or integrated with Buildbot setups.

Buildbot vs GitLab CI

Overview