Begin by enabling sonarqube functionality from within jenkins plugin - PDF document

Begin by enabling sonarqube functionality from within jenkins plugin manager Sonarqube should be installed on the same machine as jenkins.

Sonarqube could take a few minutes to start.

THe default login is admin/admin.

We need to create a token that can be shared from jenkins to sonarqube so that they can communicate securely.

I created a token called jenkinstoken (doesn’t matter what you call it). THe important thing is to copy your code so that you can import it to jenkins in a second.

Look at jenkins credentials

You might not have had that credential from above (but you should have if you configured a slave node for jenkins builds). Anyways, you need to create a secret text credential. The secret is the token you got from sonarqube.

In your petclinic repo edit ‘sonar-project.properties’. The file might already exist as well. Change the line that has the projectName to your first name After you have added the file to your git repo. Configure your jenkins project with an additional build step to execute sonarqube scanner , you should fill in the path to project properties with sonar-project.properties . Run the build job. If you are successful, you should see a new project show up on sonarqube that shows you some amazing facts about your project.