Feedback Loop 2

The second feedback loop is Code Quality Analysis using SonarQube. Read the previous section.

Jenkins Job2 for Sonar

Name Jenkins job and define log rotation strategy

Specify where sonar runner is available

Restrict where the project can be run and download the source code

Specify checkout strategy

Here we don't have sonar-project.properties inside source code, hence we download it from Jenkins config file store and then add it to the check-out folder

Since config files are generally copied to Jenkins master, we move it to the build machine and hence use a variable $sonar as a carrier

We add a build step using Sonarqube plugin for Jenkins and configure it to use the sonar-runner as defined in Jenkins System configuration page

Feedback

The jenkins console log looks as below.

Click the SonarQube icon and it will open up the sonarqube home page/dashboard as you have configured on the server.

Here you are on the Sonar Dashboard, each of the orange highlighted ones (and many more hyperlinks) opens up information that is great feedback for developers.