Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Buildbot
Buildbot

46
61
+ 1
24
GitLab CI
GitLab CI

1.2K
815
+ 1
46
Add tool

Buildbot vs GitLab CI: 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, GitLab CI is detailed as "GitLab integrated CI to test, build and deploy your code". 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.

Buildbot and GitLab CI can be primarily classified as "Continuous Integration" tools.

"Highly configurable builds" is the primary reason why developers consider Buildbot over the competitors, whereas "Robust CI with awesome Docker support" was stated as the key factor in picking GitLab CI.

Buildbot is an open source tool with 4K GitHub stars and 1.37K GitHub forks. Here's a link to Buildbot's open source repository on GitHub.

WebbyLab, Infoxchange, and Dial Once are some of the popular companies that use GitLab CI, whereas Buildbot is used by Mozilla, Animoto, and Fetch Robotics. GitLab CI has a broader approval, being mentioned in 210 company stacks & 93 developers stacks; compared to Buildbot, which is listed in 7 company stacks and 6 developer stacks.

- No public GitHub repository available -

What is Buildbot?

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.

What is GitLab CI?

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.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Buildbot?
Why do developers choose GitLab CI?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
      Be the first to leave a con
      What companies use Buildbot?
      What companies use GitLab CI?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Buildbot?
      What tools integrate with GitLab CI?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to Buildbot and 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.
      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.
      Bitbucket
      Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.
      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.
      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.
      See all alternatives
      Decisions about Buildbot and GitLab CI
      Joshua Dean K眉pper
      Joshua Dean K眉pper
      CEO at Scrayos UG (haftungsbeschr盲nkt) | 10 upvotes 96.4K views
      atScrayos UG (haftungsbeschr盲nkt)Scrayos UG (haftungsbeschr盲nkt)
      GitLab CI
      GitLab CI
      GitLab
      GitLab
      GitLab Pages
      GitLab Pages
      Jenkins
      Jenkins

      We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.

      While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.

      We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.

      See more
      Sebastian Dellwig
      Sebastian Dellwig
      Tech Lead at Porsche Digital GmbH | 6 upvotes 77.4K views
      GitLab CI
      GitLab CI
      CircleCI
      CircleCI
      Codeship
      Codeship

      We are using GitLab CI and were very happy with it. The integration of all tools like CI/CD, tickets, etc makes it very easy to stay on top of things. But be aware, Gitlab currently does not have iOS build support. So if you want to exchange that for CircleCI / Codeship to have to invest some effort. We are using a managed Mac OS device and installed the Gitlab runner there, to have iOS builds.

      See more
      Interest over time
      Reviews of Buildbot and GitLab CI
      No reviews found
      How developers use Buildbot and GitLab CI
      Avatar of Trusted Shops GmbH
      Trusted Shops GmbH uses GitLab CIGitLab CI

      We use Gitlab CI to unit and component test all of our application/components/modules. Therefore we use Docker runners.

      Avatar of Dynamictivity
      Dynamictivity uses GitLab CIGitLab CI

      GitLab CI is extremely flexible and easy to use. We also enjoy the elastic build infrastructure which is Docker based.

      Avatar of Sanghyun Park
      Sanghyun Park uses GitLab CIGitLab CI

      Upon push, build the site and publish to Google Cloud Storage.

      Avatar of cslasher
      cslasher uses GitLab CIGitLab CI

      CI/CD with Docker support.

      Avatar of WeeBull
      WeeBull uses BuildbotBuildbot

      Continuous Integration

      Avatar of Solcast
      Solcast uses GitLab CIGitLab CI

      Deployment pipeline

      How much does Buildbot cost?
      How much does GitLab CI cost?
      Pricing unavailable
      News about Buildbot
      More news
      News about GitLab CI
      More news