Description / Features
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.
It supports all languages.
Here's an example of HTML report that you can download:
- Install the plugin through the Update Center or download it into the SONARQUBE_HOME/extensions/plugins directory
- Restart the SonarQube server
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 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:
To get a local report:
- To get an HTML report, set the
true. To set the location of the HTML report, set the
sonar.issuesReport.html.locationproperty: absolute or relative path to the SonarQube working directory; default is .sonar/issues-report.html for the SonarQube Runner and Ant, target/sonar/issues-report.html for Maven.
- To display a short report in the console, set the
sonar.inclusionsproperty can be set.
com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.