Gerrit website, Git code review, patchsets, permissions, CI/CD, plugins

Gerrit

A website and open-source code review platform for Git-based development, patchset review, fine-grained permissions, CI/CD integration, plugins, and large engineering teams.

Main website

gerritcodereview.com is the main public website for Gerrit Code Review.

Core model

Open-source Git code review with patchsets, inline comments, approval rules, permissions, APIs, plugins, and CI/CD hooks.

Domain created

Who.is lists gerritcodereview.com as created on March 5, 2015.

Gerrit Code Review is an open-source Git code review platform built around patchsets, approvals, permissions, plugins, and CI/CD integration.View logo on Gerrit Code Review

What Gerrit is

Gerrit Code Review official site presents Gerrit as an open-source, patchset-based code review platform for Git-based development. It is designed for teams that need structured review, approvals, permissions, and integration with build and test systems.

Who uses Gerrit

Gerrit is used by large open-source projects, platform teams, infrastructure groups, enterprise engineering organizations, and teams with strict review gates. The site names projects such as Android, Chromium, OpenInfra Foundation, JGit, and Qt as examples of Gerrit code review workflows.

How the website works

The website introduces Gerrit, points visitors to downloads, documentation, source code, releases, plugins, roadmaps, builds, reviews, code search, community forums, Discord, and support options. It is both a project homepage and a launch point for operating or contributing to Gerrit.

Patchset-based review

Gerrit organizes code review around patchsets. A proposed change can be updated repeatedly, reviewed inline, approved through labels, and tested before it lands. This model resembles email patch review in spirit while giving teams a web interface, history, permissions, and automation hooks.

Permissions and scale

Fine-grained permissions are central to Gerrit. Organizations can control who may read repositories, push changes, review, approve, submit, administer projects, or use specific branches. That makes Gerrit attractive for large projects where different teams, repositories, and release branches need different rules.

CI/CD and plugins

Gerrit integrates with CI/CD systems through APIs, webhooks, plugins, and build-status workflows. The official site highlights Jenkins, GitHub Actions connections through plugins, custom webhooks, and Zuul-style gating, where tests can run before changes are merged.

Strengths and limits

Gerrit is strong when review quality, auditability, permissions, and pre-merge testing matter more than social coding features. Its limits are mostly cultural and operational: teams used to pull requests may need to learn patchset workflows, and administrators need to plan plugins, access rules, upgrades, and scaling.

Why it matters

Code review is one of the places where software quality, security, and team culture meet. Gerrit matters because it gives projects a rigorous review system that can scale to very large repositories and thousands of contributors while still staying open source and Git-native.

WHOIS domain data

Data pulled: May 24, 2026View current WHOIS record

Domain: gerritcodereview.com
IP address: 216.239.32.29
Registrar: MarkMonitor Inc.
WHOIS server: whois.markmonitor.com
Referral URL: http://www.markmonitor.com
Created: March 5, 2015
Updated: February 1, 2026
Expires: March 5, 2027
Nameservers: ns1.googledomains.com (216.239.32.99); ns2.googledomains.com (216.239.34.99); ns3.googledomains.com (216.239.36.99); ns4.googledomains.com (216.239.38.99)
Domain status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited; clientTransferProhibited https://icann.org/epp#clientTransferProhibited; clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited; clientUpdateProhibited (https://www.icann.org/epp#clientUpdateProhibited); clientTransferProhibited (https://www.icann.org/epp#clientTransferProhibited); clientDeleteProhibited (https://www.icann.org/epp#clientDeleteProhibited)
Registrant organization: Google LLC
Contact note: Who.is lists a MarkMonitor request-email form for registrant and technical contact email.

Key concepts

PatchsetA version of a proposed code change that can be reviewed, updated, tested, and approved before submission.
Approval labelsConfigurable review signals that decide whether a change is ready to land.
Submit ruleProject policy that controls when a reviewed change may be merged into a target branch.

Common uses

Running structured code review for large Git repositories and multi-team software projects.
Enforcing review, permission, and testing requirements before code enters protected branches.
Integrating code review with Jenkins, Zuul, custom webhooks, plugins, and other CI/CD systems.

Common misconceptions

Gerrit is not just another GitHub-style pull request interface; its patchset workflow has different review habits and terminology.
Fine-grained permissions are powerful, but they require careful administration and clear project rules.
Gerrit can support small teams, but its biggest advantages usually appear in projects that need rigorous review gates and scale.

Open questions

How can patchset-based review remain approachable for developers who learned collaboration through pull requests?
Which CI/CD and policy integrations should be built into a review platform versus handled by plugins?
How should large projects balance strict review gates with contributor speed and onboarding?