Inesh Hettiarachchi

Using CRACode Review

Bug Detection

Code Clarity

Goals

❖ Start CRA actively on All

Services

❖ Better awareness of the Code

Review Process

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.

Theres Always a Time for a Question

In-between

CRA -1Reports violations as pull request comments

CRA -2Enforces quality with merge checks

https://marketplace.atlassian.com/plugins/ch.mibex.stash.cra/server/overview

https://pmd.github.io/

http://checkstyle.sourceforge.net/

❖ Checkstyle , PMD Code Cap

❖ Setting a time line

END.