Gerrit Training — Code Review Workflow, Git-Based Review & Enterprise Administration

What Is Gerrit?

Gerrit is a Git-based code review platform that pioneered the "push-for-review" workflow. Unlike GitHub/GitLab's pull-request model, Gerrit uses a change-based review model where each commit is an independent review unit. Gerrit's per-commit review, verified label (CI integration), and submit model provide fine-grained control and auditability. Originally developed at Google for Android (AOSP), Gerrit is used by organizations that need rigorous, per-commit code review workflows — particularly in open-source projects, semiconductor/embedded systems, and telecom.

Role in Modern Software Delivery

Gerrit is a specialized code review platform — not a general-purpose Git hosting platform. GitHub, GitLab, and Bitbucket have broader adoption for general development. Gerrit's strength is in its rigorous review model: every commit is independently reviewed, verified, and submitted. This model excels in regulated environments and large open-source projects. For organizations evaluating Gerrit vs. GitHub/GitLab: if per-commit review, strong CI integration with the Verified label, and deep access control are requirements, Gerrit is a strong candidate.

Who Should Attend

• DevOps engineers administering Gerrit instances
• Software engineers working on Gerrit-managed projects (Android, AOSP, Linux kernel)
• Engineering managers evaluating Gerrit vs. GitHub/GitLab for code review

Learning Outcomes

• Master Gerrit's change-based review workflow — push, review, verify, submit
• Administer Gerrit — projects, access control, groups, permissions
• Configure the Verified label with Jenkins for CI/CD integration
• Use Gerrit's query language for change search and dashboard filtering
• Plan Gerrit→GitHub/GitLab migration where appropriate

Course Modules

1. Gerrit Fundamentals — Change-based review model. Push-for-review. Changes, patch sets. Labels and submit.
2. Gerrit Workflow — Commit-msg hook. Change-Id. Review workflow. Addressing feedback. Rebasing changes.
3. Gerrit Administration — Projects. Access control (refs/*). Groups. Plugins. Backup and upgrade.
4. CI/CD Integration — Jenkins Gerrit Trigger. Verified label. Build+vote workflow. SonarQube integration.
5. Migration Context — Gerrit vs. GitHub/GitLab. When Gerrit is the right choice. Gerrit→GitHub migration patterns.
6. Capstone: Gerrit Workflow — Configure a Gerrit project with access control and Jenkins Verified integration.

Hands-on Labs (10 total)

Push changes through Gerrit review workflow. Configure project access control. Set up Jenkins Gerrit Trigger with Verified voting. Use Gerrit query language to build a custom dashboard. Evaluate Gerrit vs. GitHub for a sample team.

Enterprise Use Cases

• Per-commit code review with mandatory CI verification for Android platform development
• Gerrit access control for 500+ contributors in an open-source project with tiered permissions
• Gerrit→GitHub Enterprise migration for teams seeking broader platform features

Related Courses

See Git Training, GitHub Admin, and GitOps Training.