See https://docs.sonarqube.org/display/SONAR/Documentation for current functionality
It is recommended to run project analyses on a regular basis to get the best from the SonarQube platform. Continuous Integration servers are the perfect tools to do so.
Install and configure the SonarQube Jenkins plugin.
Install and configure the SonarQube Hudson plugin.
Analysing a C# project built with TFS 2013 is straightforward with help of the C# Plugin and MSBuild Runner.
We're currently working to provide some SonarQube Build.VNext tasks. By adding those tasks to some existing build definitions, it will be straightforward to analyse any C#, C++ and Java projects from Build.VNext.
Apache Continuum 1.2
The difficulty in Continuum is to be able to synchronize an
install goal with the
sonar:sonar goal because it is necessary that an
install goal is run before the SonarQube collect starts (See Analyzing Source Code for more information).
Since Continuum does not provide mechanism to trigger a build from a build, there are two options: either running
install goals regularly (for example every hour), or trigger a complete command such as:
In this case, unit tests are going to be run twice: once during
install and once during
In case you decide to run
install commands regularly, here is the setup you can do for the SonarQube build:
- Create a build definition with the goal:
For multi-module projects, make sure that the --non-recursive build definition argument is NOT set.
- Once created, run this build definition on the root pom of the projects you want to SonarQube.
- For multi-module projects, make sure to check For multi modules project, load only root as recursive build when you create the project through the Continuum Maven 2 wizard
In CruiseControl, use the | to run the
install and the
sonar:sonar goals in two different processes. The command to be run should look like:
A Gerrit plugin is available to report issues on patchsets in your Gerrit server.
See the project home for more information.
These are the build configuration steps you need to do for the build:
- In general settings, make sure that fail build if at least one test failed is unchecked.
In build runner config, select Maven2, with the goal
Additional Maven command line parameters:
- In build triggering select a daily schedule (or what you prefer).
- In Properties and environment variables, add an environment variable called MAVEN_OPTS, and set the value to