Full documentation for SonarQube has moved to a new location: http://docs.sonarqube.org/display/SONAR

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The Issues Report plugin provides the ability to run local SonarQube analyses on your machine. The main use case is for developers to check the code they have added or changed before pushing it back to the SCM.

It generates an HTML report that displays a list of issues that can be filtered by severity, new issues only (comparison made against the latest version available on the remote server), etc.

...

  1. Install the plugin through the Update Center or download it into the SONARQUBE_HOME/extensions/plugins directory
  2. Restart the SonarQube server

 Usage

Note that you do not need to install any SonarQube server and database on your local machine. Just install and configure your favorite analyzer (SonarQube RunnerMaven or Ant).

Then, copy Basically, the way to run remote and local analyses is the same. Copy on your local machine the analysis configuration file (sonar-project.properties, pom.xml, etc.) that is used to analyze the project on the remote server. Make sure that the sonar.sources property  property refers to the directory containing the source code on your local machine (or update it accordingly). The tree structure of the source code on your local machine must match the tree structure that has been remotely analyzed by SonarQube. Finally, run a local analysis:

Code Block
languagebash
# Set the "sonar.dryRun" property to "true" to run a local analysis
sonar-runner -Dsonar.dryRun=true

...