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 12 Next »

Table of Contents

Prerequisites

  • Running instances of Hudson and SonarQube
  • SonarQube Hudson plugin installed on Hudson

Configuring the SonarQubeHudson Plugin

Adding SonarQubeServer

You can define as many SonarQubeservers as you wish. Then for each Hudson job, you will be able to choose on which server to run the SonarQubeanalysis.

To add a SonarQubeserver, just follow the three steps below:

1. Log into Hudson as an administrator and go to Manage Hudson > 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 your SonarQube analyses with the SonarQube Runner. Skip this step if you want to trigger your analyses with Maven.

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

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

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



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


  • No labels