Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
titleheightTable of Contents10

Table of Contents

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.

Atlassian Bamboo

Install the SonarQube plugins for Bamboo, by Marvelution.

Apache Continuum 1.2


Code Block
mvn clean install sonar:sonar -Dmaven.test.failure.ignore=true

In this case, unit tests are going to be run twice: once during install and once during sonar:sonar

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:
Code Block

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



Code Block
clean install -Dtest=false -DfailIfNoTests=false | sonar:sonar -Psonar_profile

Jetbrains TeamCity

These are the build configuration steps you need to do for the build:

  1. In general settings, make sure that fail build if at least one test failed is unchecked.
  2. In build runner config, select Maven2, with the goal

    No Format
    clean install sonar:sonar

    Additional Maven command line parameters:

    No Format
  3. In build triggering select a daily schedule (or what you prefer).
  4. In Properties and environment variables, add an environment variable called MAVEN_OPTS, and set the value to -Xmx512m

Documentation has been moved to

Documentation has been moved to