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 3 Next »


Not yet released.

Description / Features

The 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 list violations that can be filtered by new violations only, severity, etc. See the following example.

It is compatible with any language.

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 
  • To display a short report on the console, set the 'sonar.issuesReport.console.enable' to 'true'
  • Utilisation de la nouvelle propriété Sonar -Dsonar.inclusions=**/monFichier.toto pour limiter les fichiers à analyser
  • Support du tracking des violations

To generate

Unit Tests and Code Coverage Reports

Reports from JsTestDriver can be imported into Sonar.

Sample projects are available on github that can be browsed or downloaded:

  1. JavaScript project analyzed with the Sonar Runner reusing unit tests and code coverage reports generated with JsTestDriver: /projects/languages/javascript/javascript-sonar-runner-JsTestDriver
  2. JavaScript project analyzed with Maven running unit tests and code coverage reports with JsTestDriver (integrated through jstd-maven-plugin): /projects/languages/javascript/javascript-maven-JsTestDriver

Metrics

See Metrics documentation page.

Extending Coding Rules using XPath

New coding rules can be added using XPath. See the related documentation.

To navigate the AST, download the SSLR JavaScript Toolkit.

Change Log

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

 

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

 

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

 

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

 

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

  • No labels