Implementing Effective Code Review (CR) with Gerrit: Benefits, Process, and Future Plans

Background As platforms become richer in functionality, code complexity and volume increase, making problem diagnosis and modification more painful and costly. Relying solely on testing cannot guarantee full coverage, especially for low‑level logic, so early code review (CR) is essential for maintaining quality and reducing future effort.

Benefits of Code Review (CR) CR, or code review, is a systematic examination of code for standards, structure, and quality. Its four main benefits are: improving code quality, fostering knowledge sharing, deepening project understanding, and enhancing team communication.

Improving Code Quality Detecting defects early dramatically reduces correction costs, which grow exponentially from requirements to production. CR helps uncover hidden defects during the coding phase, thereby raising overall quality.

Knowledge Sharing Review sessions allow developers to learn best practices, share architectural designs, and identify gaps, accelerating onboarding for new members and enabling experienced engineers to refine their knowledge.

Deepening Project Awareness By reviewing others' code, developers quickly grasp the codebase structure and design intent, reducing mis‑understandings, facilitating feature development, and easing integration of new team members.

Promoting Team Communication CR creates a friendly environment for constructive feedback, improving collaboration and making the workplace more harmonious.

How to Conduct CR The team adopted Gerrit, an open‑source Git code‑review tool, replacing GitLab merge requests. Gerrit enforces mandatory reviews before merging, supports multiple reviewers, fine‑grained permissions, and integrates with Jenkins for automated verification.

Gerrit Advantages

Key advantages include: multiple independent reviewers, enforced pre‑merge reviews, support for multiple patch sets per change, detailed project/branch permission control, and plugins for Jenkins integration to avoid superficial reviews.

Gerrit Usage Flow

The workflow replaces git push with git review , submits changes to Gerrit for review, and after manual and Jenkins verification, synchronizes the code back to GitLab via the Gerrit‑replication plugin.

CR Process Promotion Plan To sustain CR adoption, the team lowers learning barriers by wrapping git review in a user‑friendly tool, provides regular training and documentation, integrates Jenkins for automated testing before review, and collects metrics on submission volume, review effectiveness, and efficiency.

Metrics visualized in figures show trends in code submissions, review quality, and review speed over several weeks, helping identify bottlenecks and the impact of holidays.

CR Expansion

Beyond core review, Gerrit is combined with Jenkins and GitLab to enable CI pipelines, trigger pre‑commit tests, and automate deployments after merges. The team also uses GitLab issues to track Gerrit change history by embedding issue IDs in commit messages and syncing them via Jenkins.

Future Plans Planned enhancements include adding unit‑test coverage display in the review UI, mining review data for analytics and developer profiling, and packaging the CR platform for plug‑and‑play adoption by other departments.