|Latest version||1.8.1 (2 February 2012)|
|Download||Use Hudson/Jenkins Update Center|
|License||GNU LGPL 3|
Description / Features
The plugin enables to trigger Sonar analysis from Hudson/Jenkins.
Before upgrading please read the upgrade guide.
The analysis of projects by Sonar will add time to the build process of your projects. For continuous inspection of your projects, we advice to run one Sonar analysis a day.
Depending on your needs, you can achieve that by:
- cloning your Jenkins job and add build it one time a day,
- or using the trigger functionality to prevent the execution of Sonar for builds that are triggered by SCM or by dependencies.
We suggest to use the trigger functionality as it will prevent duplication of your projects.
- Reassign Jobs to Another Sonar Instance
- If you want to build the Sonar Jenkins plugin, you can find the documentation here.
Error rendering macro 'jiraissues' : JIRA project does not exist or you do not have permission to view it.
Don't use this version as it contains critical bug - SONARPLUGINS-1455
Before upgrade please make a backup of your Hudson configuration and carefully read following notes.
If you are using version above 1.2, then before upgrade make sure that your jobs was saved with proper configuration. In order to do it, execute following script from Hudson Script Console:
If you are using version below 1.2, then:
This version introduces some changes to configuration files. Upgrade will be performed automatically, but before upgrade please make a backup of your Hudson configuration.
Most probably next plugin version will be incompatible with versions below 1.2, so it's highly recommended to update to this version.
When upgrading to this version, please be aware that "Skip on SCM build" (Default Yes) is becoming "Poll SCM" (Default No) under Triggers section. Due to technical limitation, this data could not be migrated to 1.1, and therefore if it was unchecked in certain jobs, the new box should be manually checked.