Automated code review process

Automated code review process

• 1.
  Automated Code Review Process BySandesh Sharma
• 2.
  Contents  Problem Statement  Available Tools −Gerrit − SONAR
• 3.
  Problem Statement  Should CoverFollowing Requirements − Architecture & Design − Comments − Coding Rules − Potential Bugs − Complexity − Unit Tests − Duplications  Can Integrate with Continuous Integration Environment (CI Integration with SVN, Maven and Ant Build)  Create task using the JIRA on bugs  Running locally  Collaboration and Manual Code review Process  Maintenance
• 4.
  Gerrit  A Basic Commit-to-DeployPipeline  Collaborative Approach (Peer to Peer Code Review)  Developer Notifications  Dashboard & Reports  Sharing across  Multiple branches with Gerrit + Jenkins  The Human Factor  Pro-tips/best practices
• 5.
  Gerrit
• 6.
  Gerrit
• 7.
  The Gerrit Flow gerritupstream dev-adev-b
• 8.
  Flow of changes Create Local Branch %git checkout -b topic-branch work Push to Gerrit % git push gerrit HEAD:refs/for/master
• 9.
  Flow of changes Create Local Branch work Push to Gerrit Review Fix commit Upstreamrepo rejected approved/ submitted rebased!
• 10.
  rejected Your development work-flow incommands  git checkout -b local-topic-branch  work work work  git rebase -i upstream/master # fix up commits  git push gerrit HEAD:refs/for/master  Create new commits based on reviews  git rebase -i upstream/master # squash up  git push gerrit HEAD:refs/for/master
• 11.
  SONAR  Community based freesoftware distribution Under the license LGPL v3.  Bigger Code Quality Matrix with wide range of plug-ins.  Integration with − Maven − JIRA − SVN − Eclipse − Ant  Interactive Reports  API Doc’s creation
• 12.
  SONAR
• 13.
  SONAR Project Dashboard
• 14.
  SONAR Defect Detection
• 15.
  SONAR Design Analysis: PackageCycles
• 16.
  thAnks ersandeshsharma [at] gmail.com