Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 43 Next »

Table of Contents

Prerequisites

Configuring the SonarQubeTM Jenkins Plugin

Adding SonarQubeTM Server

You can define as many SonarQubeTM servers as you wish. Then for each Jenkins job, you will be able to choose on which server to run the SonarQubeTM analysis.

To add a SonarQubeTM server, just follow the three steps below:

1. Log into Jenkins as an administrator and go to Manage Jenkins > Configure System: 



2. Scroll down to the Sonar configuration section and click on Add Sonar:


3. Configure your SonarQubeTM installation:

Adding Sonar Runner

This step is mandatory if you want to trigger your SonarQubeTM analyses with the Sonar Runner. Skip this step if you want to trigger your analyses with Maven.

You can define as many Sonar Runner launchers as you wish. Then for each Jenkins job, you will be able to choose with which launcher to run the SonarQubeTM analysis.

To add a Sonar Runner, just follow the three steps below:

1. Log into Jenkins as an administrator and go to Manage Jenkins > Configure System: 



2. Scroll down to the Sonar Runner configuration section and click on Add Sonar Runner. It is based on the typical Jenkins tool auto-installation. You can either choose to point to an already installed version of Sonar Runner (uncheck 'Install automatically') or tell Jenkins to grab the installer from a remote location (check 'Install automatically'):


  • No labels