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: