Book Image

Learning Gerrit Code Review

By : Luca Milanesio
Book Image

Learning Gerrit Code Review

By: Luca Milanesio

Overview of this book

<p>Developing software is now more than ever before a globally distributed activity: agile methodologies that worked well enough with co-located teams now need to be empowered with additional tools such as Gerrit code review to allow the developers to share, discuss, and cooperate in a more social way, even with GitHub.</p> <p>Learning Gerrit Code Review is a practical guide that provides you with step-by-step instructions for the installation, configuration, and use of Gerrit code review. Using this book speeds up your adoption of Gerrit through the use of a unique, consolidated set of recipes ready to be used for LDAP authentication and to integrate Gerrit with Jenkins and GitHub.</p> <p>Learning Gerrit Code Review looks at the workflow benefits of code review in an agile development team, breaks it down into simple steps, and puts it into action without any hassle. It will guide you through the installation steps of Gerrit by showing you the most typical setup and configuration schemes used in private networks.</p> <p>You will also learn how to effectively use Gerrit with GitHub in order to provide the ability to add more consistent code review functionality to the social collaboration tools provided by the GitHub platform. Using the two tools together, you will be able to reuse your existing accounts and integrate your GitHub community into the development lifecycle while keeping in touch with external contributors.</p>
Table of Contents (17 chapters)
Learning Gerrit Code Review
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Automated code validation


The Jenkins and Gerrit setup is complete and now we can see how it plugs into the Gerrit review workflow. When the change is pushed to Gerrit for review, a new build gets automatically triggered on the Jenkins job that was previously configured.

The Jenkins job page shows the result of pushing the new change. It is similar to a normal Continuous Integration execution whereby an additional small G icon with two numbers indicating the change number and patch-set number represents the Gerrit trigger activation and points to the original change/patch-set built.

Additionally, the Gerrit trigger plugin adds comments to the Gerrit change in order to report any activity to the change author and reviewers. This is precious information for the other reviewers that are working on the assessment of the patch-set. A change that has been successfully validated by a build and unit test execution should be more stable and then can take a higher priority for being assessed by Gerrit reviewers.

If the build is successful, the Gerrit trigger plugin submits positive feedback on the Gerrit change with a Verified/+1 score. The following screenshot shows the Gerrit trigger plugin submit a Verified + 1: