You are viewing an old version of this page. View the current version.
Compare with Current ·
View Page History
 | This page documents how to configure the Sonar Jenkins plugin for versions 2.0+. For versions prior to 2.0, browse this documentation page. |
Prerequisites
- Running instances of Jenkins and Sonar
- Sonar Jenkins plugin installed on Jenkins
Configuring the Sonar Jenkins Plugin
Adding Sonar Server
You can define as many Sonar servers as you wish. To add a Sonar 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 Sonar installation:
Parameters
Name | Mandatory | Description |
|---|---|---|
Name | Yes | The logical name of the server |
Disable | No | Check it if you want to disable this server |
Server URL | Yes | The URL to access your Sonar server (default to http://localhost:9000). This is the URL used when the analysis will be launched by Jenkins |
Server public URL | Yes | This is the URL which the user should use to connect to Sonar. If it's not specified the Server URL will be used. |
Database URL | Yes | The JDBC URL to connect to the database hosting the Sonar database |
Database login | Yes | The login to connect to the database hosting the Sonar database |
Database password | Yes | The password to connect to the database hosting the Sonar database the password will be encrypted on the configuration file. |
Database driver | Yes | The Java driver classname to be used to connect to the database |
Version of sonar-maven-plugin | No | If you want to force the use of a specific sonar-maven-plugin, you can set it here. |
Additional properties | No | The properties you want to pass to Sonar, you must use the format : -Dsome.property=some.value -Danother.property=another.value |
Skip if triggered by SCM Changes | No | If you want to skip Sonar analysis when the Jenkins build is launched by a change in the SCM, check it |
Skip if triggered by the build of a dependency | no | If you want to skip Sonar analysis when the Jenkins build is launched by the build of a dependency, check it |
Skip if environment variable is defined | no | If the variable set is defined, Sonar analysis will be skipped |
| When using trigger exclusions, if you check multiple "Skip if ..." parameters, the build will be skip if at least one of the property is true (it's an OR condition). |
Adding Sonar Runner
Labels
