The document discusses implementing automated code review using Checkstyle and PMD across all services. It outlines goals of starting code review actively and increasing awareness of the process. The agenda includes explaining the current approach, discussing code review with developers, and setting caps for the number of allowed issues per class when merging pull requests. It also involves setting a timeline for other services to adopt code review standards and addressing any issues with the current standards file.

1. Inesh Hettiarachchi
Using CRA
Code Review
Bug Detection
Code Clarity

2. Goals
❖ Start CRA actively on All
Services
❖ Better awareness of the Code
Review Process

3. Today's menu
❖ Explain the current approach on how to implement the automated code review
❖ Review and discussion by all dev's on CRA and the current approach to
implement automated code review
❖ Setting a cap for accepted number of Checkstyle issues for a single class
when merging a pull request
❖ Setting a cap for accepted number of PMD issues for a single class when
merging a pull request
❖ Setting a time line for other services to be fully adopt the CRA Checkstyle and
PMD. Each module lead can discuss on a time line for their product in
BitBucket.
❖ Issues in current standards file.

4. Theres Always a Time for a Question
In-between

5. CRA -1
Reports violations as pull request comments

6. CRA -2
Enforces quality with merge checks

7. https://marketplace.atlassian.com/plugins/ch.mibex.stash.cra/server/overview
https://pmd.github.io/
http://checkstyle.sourceforge.net/

9. ❖ Checkstyle , PMD Code Cap

10. ❖ Setting a time line

12. END.