Jenkins SonarQube Plugin
Project homepage: http://redirect.sonarsource.com/plugins/jenkins.html
Continuous inspection: http://nemo.sonarsource.org/dashboard/index/org.jenkins-ci.plugins:sonar
Issue tracking: http://jira.sonarsource.com/browse/SONARJNKNS
If you're wanting to make changes, please clone the git repository at
With jenkins-sonar-plugin, you can configure SonarQube instances and run a SonarQube Scanner analysis in several ways:
- By injecting the SonarQube configuration as environment variables and using them in any job step (such as Maven, Ant, Gradle, ...);
- Using the Sonar Scanner job;
- Using SonarQube Scanner for MSBuild's 'begin analysis' and 'end analysis' jobs;
'SonarQube Scanner' and 'SonarQube Scanner for MSBuild' are managed as installable tools. List of available versions is retrieved automatically by Jenkins/Hudson from a json file hosted on their respective update site:
For Jenkins, the files are automatically updated when a new version of Sonar Scanner or SonarQube Scanner for MSBuild is published, thanks to crawlers written in groovy:
For Hudson, it seems it is a manual process and we should ask on the hudson dev mailing list for someone to update the json file.
Copyright 2007-2017 SonarSource.
Licensed under the GNU Lesser General Public License, Version 3.0