With the integration between Jenkins and Gerrit now complete, we have come to the end of our journey for setting up and learning how to effectively use the Code Review workflow.
Jenkins has provided the additional automation that validates the code sitting in the review inbound queue.
The automatic validation saves team members' time, which would otherwise be spent fixing broken branches. This means more effort can then be spent reading somebody else's code and increasing quality, project, and code knowledge across the team.
By validating changes through Code Review, the product backlog gets naturally prioritized. Adding more flexibility to the product roadmap, the most stable features will get completed first with the remaining features following a longer and much-needed stabilization process before getting released.