Skip to content

Code Review Pipeline⚓︎

This section provides details on the Code Review pipeline of the EDP CI/CD framework. Explore below the pipeline purpose, stages and possible actions to perform.

Code Review Pipeline Purpose⚓︎

The purpose of the Code Review pipeline contains the following points:

  • Check out and test a particular developer's change (Patch Set) in order to inspect whether the code fits all the quality gates and can be built and tested;
  • Be triggered if any new Patch Set appears in GitHub/GitLab/Gerrit;
  • Send feedback about the build process in Tekton to review the card in Gerrit;
  • Send feedback about Sonar violations that have been found during the Sonar stage.

Find below the functional diagram of the Code Review pipeline with the default stages:

flowchart TD
   build --> dockerbuild-verify
   compile --> test
   dockerbuild-verify --> stop([fa:fa-circle])
   dockerfile-lint --> dockerbuild-verify
   fetch-repository --> init-values
   fetch-repository --> helm-docs
   fetch-repository --> dockerfile-lint
   fetch-repository --> helm-lint
   helm-docs --> stop([fa:fa-circle])
   helm-lint --> stop([fa:fa-circle])
   init-values --> compile
   start([fa:fa-circle]) --> report-pipeline-start-to-gitlab
   report-pipeline-start-to-gitlab --> fetch-repository
   sonar --> build
   test --> sonar