Bitbucket vs Gerrit Code Review

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

Bitbucket

40K
32.4K
+ 1
2.8K
Gerrit Code Review

116
223
+ 1
59
Add tool

Bitbucket vs Gerrit Code Review: What are the differences?

Key Differences between Bitbucket and Gerrit Code Review

Bitbucket and Gerrit Code Review are popular tools used in software development for managing code repositories and facilitating code reviews. Although they both serve similar purposes, there are several key differences that set them apart.

  1. Integration with Git vs. Custom Version Control System: Bitbucket is built on top of Git, a widely used distributed version control system. It provides seamless integration with Git, allowing developers to easily manage their code repositories using familiar Git commands. In contrast, Gerrit Code Review has its own custom version control system called "PolyGerrit," which is specifically designed for code review workflows.

  2. Code Review Workflow: Bitbucket offers a more traditional code review workflow, where reviewers can leave comments directly on the code changes and collaboratively discuss the changes before merging. On the other hand, Gerrit Code Review introduces a more strict and structured code review process by providing a Gerrit-specific web interface for reviewers to review and score code changes. This workflow allows for finer-grained control over code quality and enforce stricter coding standards.

  3. Access Control and Permissions: Bitbucket provides a flexible and granular access control system, allowing administrators to easily manage user permissions at the repository, branch, and file level. It also integrates with popular identity providers such as LDAP and Active Directory. In contrast, Gerrit Code Review focuses on a more fine-grained access control system, where permissions can be set on a per-branch or per-project basis. It also provides built-in support for integrating with external identity providers.

  4. Support for Continuous Integration and DevOps: Bitbucket offers built-in continuous integration and continuous deployment capabilities through its integration with tools like Jenkins and Bamboo. It allows developers to automate their build, test, and deployment processes directly from Bitbucket. In contrast, Gerrit Code Review does not offer native support for continuous integration or deployment tools. However, it can be integrated with external CI/CD systems using plugins or custom integrations.

  5. Code Search and Analytics: Bitbucket provides powerful code search capabilities, allowing developers to search for code snippets, files, or specific lines of code within their repositories. It also offers built-in analytics and reporting features to track code contributions, reviewer activity, and other metrics. In contrast, Gerrit Code Review does not have native code search or analytics capabilities. However, it can be integrated with external code search tools or analytics platforms.

  6. Commercial vs. Open Source: Bitbucket is a commercial product offered by Atlassian, a software company specializing in team collaboration tools. It comes with a range of pricing plans and support options. On the other hand, Gerrit Code Review is an open-source project and is available for free under the Apache License 2.0. It is maintained by a community of contributors and can be self-hosted or deployed on cloud platforms.

In summary, Bitbucket and Gerrit Code Review differ in terms of their integration with Git, code review workflow, access control and permissions, support for CI/CD, code search and analytics features, and their pricing models (commercial vs. open source). Choosing the right tool depends on the specific needs and requirements of the development team or organization.

Decisions about Bitbucket and Gerrit Code Review
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

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
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Bitbucket
Pros of Gerrit Code Review
  • 904
    Free private repos
  • 397
    Simple setup
  • 348
    Nice ui and tools
  • 341
    Unlimited private repositories
  • 240
    Affordable git hosting
  • 123
    Integrates with many apis and services
  • 119
    Reliable uptime
  • 87
    Nice gui
  • 85
    Pull requests and code reviews
  • 58
    Very customisable
  • 16
    Mercurial repositories
  • 14
    SourceTree integration
  • 12
    JIRA integration
  • 10
    Track every commit to an issue in JIRA
  • 8
    Deployment hooks
  • 8
    Best free alternative to Github
  • 7
    Automatically share repositories with all your teammates
  • 7
    Compatible with Mac and Windows
  • 6
    Source Code Insight
  • 6
    Price
  • 5
    Login with Google
  • 5
    Create a wiki
  • 5
    Approve pull request button
  • 4
    Customizable pipelines
  • 4
    #2 Atlassian Product after JIRA
  • 3
    Also supports Mercurial
  • 3
    Unlimited Private Repos at no cost
  • 3
    Continuous Integration and Delivery
  • 2
    Academic license program
  • 2
    Multilingual interface
  • 2
    Teamcity
  • 2
    Open source friendly
  • 2
    Issues tracker
  • 2
    IAM
  • 2
    IAM integration
  • 2
    Mercurial Support
  • 13
    Code review
  • 11
    Good workflow
  • 10
    Cleaner repository story
  • 9
    Open source
  • 9
    Good integration with Jenkins
  • 5
    Unlimited repo support
  • 2
    Comparison dashboard

Sign up to add or upvote prosMake informed product decisions

Cons of Bitbucket
Cons of Gerrit Code Review
  • 19
    Not much community activity
  • 17
    Difficult to review prs because of confusing ui
  • 15
    Quite buggy
  • 10
    Managed by enterprise Java company
  • 8
    CI tool is not free of charge
  • 7
    Complexity with rights management
  • 6
    Only 5 collaborators for private repos
  • 4
    Slow performance
  • 2
    No AWS Codepipelines integration
  • 1
    No more Mercurial repositories
  • 1
    No server side git-hook support
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

    What is 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.

    What is Gerrit Code Review?

    Gerrit is a self-hosted pre-commit code review tool. It serves as a Git hosting server with option to comment incoming changes. It is highly configurable and extensible with default guarding policies, webhooks, project access control and more.

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

    What companies use Bitbucket?
    What companies use Gerrit Code Review?
    See which teams inside your own company are using Bitbucket or Gerrit Code Review.
    Sign up for StackShare EnterpriseLearn More

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

    What tools integrate with Bitbucket?
    What tools integrate with Gerrit Code Review?

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

    Blog Posts

    Mar 4 2020 at 5:14PM

    Atlassian

    GitBitbucketWindows+4
    3
    1064
    GitHubGitDocker+34
    29
    42467
    What are some alternatives to Bitbucket and Gerrit Code Review?
    GitHub
    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
    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.
    Git
    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
    Atlassian Stash
    It is a centralized solution to manage Git repositories behind the firewall. Streamlined for small agile teams, powerful enough for large organizations.
    Crucible
    It is a Web-based application primarily aimed at enterprise, and certain features that enable peer review of a code base may be considered enterprise social software.
    See all alternatives