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

Buildbot

70
118
+ 1
27
GitLab

51.5K
43.5K
+ 1
2.4K
Add tool

Buildbot vs GitLab: 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; GitLab: Open source self-hosted Git management software. GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.

Buildbot belongs to "Continuous Integration" category of the tech stack, while GitLab can be primarily classified under "Code Collaboration & Version Control".

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

  • Manage git repositories with fine grained access controls that keep your code secure
  • Perform code reviews and enhance collaboration with merge requests
  • Each project can also have an issue tracker and a wiki

"Highly configurable builds" is the primary reason why developers consider Buildbot over the competitors, whereas "Self hosted" was stated as the key factor in picking GitLab.

Buildbot and GitLab are both open source tools. GitLab with 20.1K GitHub stars and 5.33K forks on GitHub appears to be more popular than Buildbot with 3.98K GitHub stars and 1.36K GitHub forks.

According to the StackShare community, GitLab has a broader approval, being mentioned in 1219 company stacks & 1431 developers stacks; compared to Buildbot, which is listed in 7 company stacks and 6 developer stacks.

Decisions about Buildbot and GitLab
Weverton Timoteo

Do you review your Pull/Merge Request before assigning Reviewers?

If you work in a team opening a Pull Request (or Merge Request) looks appropriate. However, have you ever thought about opening a Pull/Merge Request when working by yourself? Here's a checklist of things you can review in your own:

  • Pick the correct target branch
  • Make Drafts explicit
  • Name things properly
  • Ask help for tools
  • Remove the noise
  • Fetch necessary data
  • Understand Mergeability
  • Pass the message
  • Add screenshots
  • Be found in the future
  • Comment inline in your changes

Read the blog post for more detailed explanation for each item :D

What else do you review before asking for code review?

See more
Weverton Timoteo

Using an inclusive language is crucial for fostering a diverse culture. Git has changed the naming conventions to be more language-inclusive, and so you should change. Our development tools, like GitHub and GitLab, already supports the change.

SourceLevel deals very nicely with repositories that changed the master branch to a more appropriate word. Besides, you can use the grep linter the look for exclusive terms contained in the source code.

As the inclusive language gap may happen in other aspects of our lives, have you already thought about them?

See more
Weverton Timoteo

One of the magic tricks git performs is the ability to rewrite log history. You can do it in many ways, but git rebase -i is the one I most use. With this command, It’s possible to switch commits order, remove a commit, squash two or more commits, or edit, for instance.

It’s particularly useful to run it before opening a pull request. It allows developers to “clean up” the mess and organize commits before submitting to review. If you follow the practice 3 and 4, then the list of commits should look very similar to a task list. It should reveal the rationale you had, telling the story of how you end up with that final code.

See more
Kamaleshwar BN
Senior Software Engineer at Pulley · | 8 upvotes · 477.2K views

Out of most of the VCS solutions out there, we found Gitlab was the most feature complete with a free community edition. Their DevSecops offering is also a very robust solution. Gitlab CI/CD was quite easy to setup and the direct integration with your VCS + CI/CD is also a bonus. Out of the box integration with major cloud providers, alerting through instant messages etc. are all extremely convenient. We push our CI/CD updates to MS Teams.

See more

Gitlab as A LOT of features that GitHub and Azure DevOps are missing. Even if both GH and Azure are backed by Microsoft, GitLab being open source has a faster upgrade rate and the hosted by gitlab.com solution seems more appealing than anything else! Quick win: the UI is way better and the Pipeline is way easier to setup on GitLab!

See more
Nazar Atamaniuk
Shared insights
on
DeployPlaceDeployPlaceGitHubGitHubGitLabGitLab

At DeployPlace we use self-hosted GitLab, we have chosen GitLab as most of us are familiar with it. We are happy with all features GitLab provides, I can’t imagine our life without integrated GitLab CI. Another important feature for us is integrated code review tool, we use it every day, we use merge requests, code reviews, branching. To be honest, most of us have GitHub accounts as well, we like to contribute in open source, and we want to be a part of the tech community, but lack of solutions from GitHub in the area of CI doesn’t let us chose it for our projects.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Buildbot
Pros of GitLab
  • 9
    Highly configurable builds
  • 5
    Hosted internally
  • 5
    Beautiful waterfall
  • 4
    Free open source
  • 3
    Python
  • 1
    No external web fonts by default
  • 500
    Self hosted
  • 428
    Free
  • 336
    Has community edition
  • 240
    Easy setup
  • 239
    Familiar interface
  • 132
    Includes many features, including ci
  • 109
    Nice UI
  • 82
    Good integration with gitlabci
  • 55
    Simple setup
  • 33
    Has an official mobile app
  • 32
    Free private repository
  • 29
    Continuous Integration
  • 20
    Open source, great ui (like github)
  • 16
    Slack Integration
  • 11
    Full CI flow
  • 10
    Free and unlimited private git repos
  • 8
    User, group, and project access management is simple
  • 7
    All in one (Git, CI, Agile..)
  • 7
    Intuitive UI
  • 7
    Built-in CI
  • 4
    Both public and private Repositories
  • 3
    So easy to use
  • 3
    It's powerful source code management tool
  • 3
    Issue system
  • 3
    Excellent
  • 3
    Integrated Docker Registry
  • 3
    Build/pipeline definition alongside code
  • 3
    Mattermost Chat client
  • 3
    Full DevOps suite with Git
  • 3
    CI
  • 2
    Dockerized
  • 2
    It's fully integrated
  • 2
    Security and Stable
  • 2
    I like the its runners and executors feature
  • 2
    Because is the best remote host for git repositories
  • 2
    Unlimited free repos & collaborators
  • 2
    On-premises
  • 2
    Free private repos
  • 2
    Low maintenance cost due omnibus-deployment
  • 2
    Great for team collaboration
  • 2
    One-click install through DigitalOcean
  • 1
    Wounderful
  • 1
    Opensource
  • 1
    Not Microsoft Owned
  • 1
    Many private repo
  • 1
    Published IP list for whitelisting (gl-infra#434)
  • 1
    Built-in Docker Registry
  • 1
    The dashboard with deployed environments
  • 1
    Groups of groups
  • 1
    Kubernetes Integration
  • 1
    Multilingual interface
  • 1
    Kubernetes integration with GitLab CI
  • 1
    Native CI
  • 1
    HipChat intergration
  • 1
    It includes everything I need, all packaged with docker
  • 1
    Review Apps feature
  • 1
    Powerful software planning and maintaining tools
  • 1
    Powerful Continuous Integration System
  • 1
    Beautiful
  • 0
    Supports Radius/Ldap & Browser Code Edits

Sign up to add or upvote prosMake informed product decisions

Cons of Buildbot
Cons of GitLab
    Be the first to leave a con
    • 27
      Slow ui performance
    • 7
      Introduce breaking bugs every release
    • 5
      Insecure (no published IP list for whitelisting)
    • 1
      Built-in Docker Registry
    • 0
      Review Apps feature

    Sign up to add or upvote consMake informed product decisions

    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?

    GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.

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

    What companies use Buildbot?
    What companies use GitLab?
    See which teams inside your own company are using Buildbot or GitLab.
    Sign up for StackShare EnterpriseLearn More

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

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

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

    Blog Posts

    What are some alternatives to Buildbot and GitLab?
    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.
    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.
    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.
    See all alternatives