Scanning code
To scan your PL/SQL code and send the results to SonarQube, you need to run the analysis with a SonarScanner. As PL/SQL does not have a standard directory layout for project files, we recommend using the SonarScanner CLI.
For general information about how to run the analysis, see the SonarScanner CLI documentation.
These are the additional parameters that you can use with the ZPA Plugin for SonarQube:
| Parameter | Description | Default value |
|---|---|---|
sonar.plsqlopen.file.suffixes | Specifies the file suffixes for PL/SQL files to be analyzed. | sql,plb,pks,pkb. |
sonar.zpa.concurrentExecution | Enable concurrent analysis of files. | true |
sonar.zpa.forms.metadata | Path to the file containing metadata for Oracle Forms. For more details, see "Oracle Forms support". | |
sonar.zpa.errorRecoveryEnabled | Enable error recovery mode. For more details, see "Error recovery". | true |
sonar.zpa.coverage.reportPaths | Paths (absolute or relative) to report files with utPLSQL coverage data. For more details, see "Importing utPLSQL reports". | utplsql-coverage.xml |
sonar.zpa.tests.reportPaths | Paths (absolute or relative) to report files with utPLSQL test execution data. For more details, see "Importing utPLSQL reports". | utplsql-test.xml |