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 48 Current »

Table of Contents

Prerequisites

Configuring the SonarQube Jenkins Plugin

Adding SonarQube Server

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

To add a SonarQube 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 SonarQube installation:

Adding SonarQube Runner

This step is mandatory if you want to trigger any of your SonarQube analyses with the SonarQube Runner. Skip this step if you want to trigger all your analyses with Maven.

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

To add a SonarQube 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 SonarQube Runner (uncheck 'Install automatically') or tell Jenkins to grab the installer from a remote location (check 'Install automatically'):


  • No labels