Chromium Gerrit

Chromium Gerrit
Name	Chromium Gerrit
Developer	Google, The Chromium Project
Initial release	2009
Programming language	Java (programming language), JavaScript
Operating system	Linux, Windows, macOS
License	Apache License

Chromium Gerrit Chromium Gerrit is a web-based Code review tool used by the Chromium Project to manage contributions to the Chromium (web browser), Chromium OS, and related Google-led initiatives. It provides a patch management interface, integrates with Git, and coordinates review workflows among developers from organizations such as Google, Intel Corporation, ARM Limited, AMD, and independent contributors. Chromium Gerrit interfaces with continuous integration services like Buildbot, Kokoro, and other systems used across projects including Chromium Embedded Framework and Chromium for Android.

Overview

Chromium Gerrit serves as a centralized code-review front end that connects Git repositories for projects such as Chromium (web browser), V8 (JavaScript engine), Skia (graphics library), Blink (browser engine), and OpenSSL-related components. It supports per-change discussion, inline commenting, and approval labels used by teams at Google and external stakeholders like Mozilla Foundation, Samsung Electronics, and Microsoft. Gerrit instances in the Chromium ecosystem coordinate with systems like Netlify, Travis CI, and CircleCI for cross-project verification, and integrate policy tools from entities like The Linux Foundation and Foundation for Open Source Infrastructure.

Architecture and Components

The Gerrit architecture for Chromium combines a web UI, a gerrit-server backend, and integrations with Git, authentication providers such as OAuth 2.0, OpenID Connect, and LDAP. Key components include the change model, patch set storage, submit rules, and replication to mirrors hosted on infrastructure like Google Cloud Platform, Amazon Web Services, and Azure. The pipeline interoperates with Buildbot and Kokoro for CI, Jenkins where legacy jobs persist, and artifact repositories such as Google Cloud Storage and Artifactory. Data storage relies on NoteDb for metadata, and persistent services like MySQL, PostgreSQL, and Apache Cassandra are used in peripheral integrations. The UI integrates with browsers including Google Chrome, Mozilla Firefox, Microsoft Edge, and supports tools like Android Studio and Visual Studio Code through plugins.

Development Workflow and Usage

Developers working on Chromium (web browser), Chromium OS, V8 (JavaScript engine), or Skia (graphics library) typically submit changes via Git push to Gerrit change branches, request review from maintainers affiliated with organizations such as Google, Intel Corporation, ARM Limited, Samsung Electronics, and community maintainers from The Chromium Authors. The workflow uses approval labels (e.g., Code-Review, Verified) and relies on automated checks from Buildbot, Kokoro, Trybots, and static analysis tools like Clang Static Analyzer, Coverity, and AddressSanitizer. Contributors may interact through tooling such as repo (software tool), git-cl, git-review, or web UI actions, and participate in review discussions referencing bug trackers like Monorail (issue tracker), Bugzilla, and project wikis on Google Wiki and GitHub mirrors.

Integration with Chromium Project

Gerrit is tightly integrated with the Chromium Project’s repository structure including mainline trees for Chromium (web browser), Chromium OS, V8 (JavaScript engine), Skia (graphics library), and Blink (browser engine). The integration coordinates with the Chromium infra stack, Buildbucket, Swarming, and test farms run on infrastructure tied to Google Cloud Platform and partner data centers such as those run by Amazon Web Services and Microsoft Azure. Release engineering, involving teams and services like Release Engineering (Google), Continuous Integration, and build managers, uses Gerrit to gate changes for channels like Chrome Stable, Chrome Beta, and Chrome Canary. Mirrors and read-only replicas interoperate with code search services like OpenGrok and Zoekt.

Security and Access Control

Access control in the Chromium Gerrit deployment leverages authentication systems such as OAuth 2.0, OpenID Connect, and enterprise LDAP directories used by organizations like Google, Intel Corporation, Samsung Electronics, and Microsoft. Authorization is managed through Gerrit project-level permissions, ACLs, and group memberships tied to entities including The Chromium Authors, Google, and community SIGs. Security reviews coordinate with teams like Project Zero, Chromium Security, and external auditors from CVE-reporting practices; continuous verification uses fuzzers such as ClusterFuzz and sanitizers like AddressSanitizer and MemorySanitizer. Incident response and disclosure follow policies adopted by the Chromium Project and align with standards from CVE, CERT/CC, and vendor security teams at Google and partner organizations.

History and Evolution

Gerrit originated as a fork of early code-review systems and was adopted by the Chromium ecosystem to replace earlier patchwork workflows involving Rietveld (software), Patchwork, and mailing lists used by projects like Linux kernel and Apache HTTP Server. Over time, Chromium Gerrit evolved with contributions from Google engineers, community developers associated with The Chromium Authors, and integration work by companies such as Intel Corporation and Samsung Electronics. Key milestones include migration from legacy metadata stores to NoteDb, integration with Buildbot and later Kokoro and Buildbucket, and adoption of policies harmonized with OpenSSL and V8 (JavaScript engine) upstream practices. The platform continues to adapt with ongoing work involving Continuous Integration, code-health initiatives, and cross-project collaboration with entities like Mozilla Foundation and Linux Foundation.

Category:Version control systems