Skip to end of metadata
Go to start of metadata

By SonarSource – SonarSource – Issue Tracker – Supported by SonarSource
More versions
SonarPLSQL 3.3 – Oct 24, 2018 – SonarQube 6.7+ (Compatible with LTS)
13 new rules, security reports and support of Security Hotspot issue type
I accept the Terms and ConditionsDownloadRelease notes

Description

Enables the powerful SonarPLSQL analyzer.

 

First Analysis of a PL/SQL Project

  1. Install SonarQube Server (see Setup and Upgrade for more details)
  2. Install SonarQube Scanner and be sure your can call sonar-scanner from the directory where you have your source code
  3. Install SonarPLSQL (see Installing a Plugin for more details)
  4. Run your analysis with the SonarQube Scanner by executing the following command from the root directory of the project:

    sonar-scanner -Dsonar.projectKey=xxx -Dsonar.sources=.
  5. Follow the link provided at the end of the analysis to browse your project's quality in SonarQube UI

Further Analyses

Assuming steps 1-3 above have already been completed, you'll want to encapsulate your analysis parameters in a sonar-project.properties file at the root of your project (see a sample project on GitHub: https://github.com/SonarSource/sonar-scanning-examples/tree/master/sonarqube-scanner). Then subsequent analyses can simply be run with:

sonar-scanner

Data Dictionary

Accuracy of the analysis can be improved by providing properties to retrieve the data dictionary.

 

Advanced Usage

With SonarPLSQL, you can:

  • create your own Custom Rules
  • change the files to analyze by configuring the property sonar.plsql.file.suffixes in Settings > General Settings > PL/SQL > File Suffixes
  • No labels