Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Description / Features

The Issues Report plugin provides the ability to run local Sonar analyses. The main use case is for a developer to check its code before pushing it to the SCM.

It generates an HTML report that displays a list of violations that can be filtered by severity, new violations only, etc.

It support all languages.

Here's an example of HTML report that you can download:

Installation

  1. Install the Issues Report plugin through the Update Center or download it into the SONAR_HOME/extensions/plugins directory
  2. Restart the Sonar server

Usage

Run a Sonar analysis on your project with your usual analyzer (Sonar RunnerMaven or Ant).

To run the analysis without pushing the results to the database, set the 'sonar.dryRun' to 'true'. Then, the analysis will be run locally.

To get a local report:

  • To generate an HTML report, set the property 'sonar.issuesReport.html.enable' to 'true'
  • To set the localtion of this report, set the property 'sonar.issuesReport.html.location' (default is .sonar/issues-report.html)
  • To display a short report on the console, set the 'sonar.issuesReport.console.enable' to 'true'
A useful feature is to limit the scope of the analysis to the files that have been created or modified. To do so, the 'sonar.inclusions' property can be set.

Change Log

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

  • No labels