Skip to content

Release 3.5.1

Latest
Latest
Compare
Choose a tag to compare
@github-actions github-actions released this 28 Jun 00:38
· 16 commits to main since this release
3.5.1
9fa3da5
This commit was signed with the committer’s verified signature.
felipebz Felipe Zorzo
SSH Key Fingerprint: G1slwNOVsUxhEo26exLIbtH+bL+DBMgVz7HE+4oIz3U Learn about vigilant mode.

SonarQube compatibility

This release is compatible with SonarQube 9.9 LTA Community Edition and newer. However, comprehensive testing and validation have been conducted only on SonarQube 9.9 CE, 10.5 CE, and 10.6 CE. While compatibility is expected for other versions within this range, the full extent of functionality has been assured only for the tested versions.

Additionally, please note that while this version may work with SonarQube’s commercial editions, the compatibility was not tested and simultaneous analysis using ZPA and SonarSource’s embedded PL/SQL plugin is not supported. If you require this scenario, consider using zpa-cli instead.

Highlights

First-class support for test and coverage reports generated by utPLSQL

Two new properties specifically designed for consuming test and coverage reports generated by utPLSQL were added:

  • sonar.zpa.tests.reportPaths: Use this property to specify the path to the test report(s) (generated using the ut_sonar_test_reporter).
  • sonar.zpa.coverage.reportPaths: Similarly, this property allows you to specify the path to the coverage report(s) (generated using the ut_coverage_sonar_reporter).

Previously, importing test and coverage reports into SonarQube required generic properties. However, with the introduction of these new properties, the ZPA plugin can now automatically associate the test and coverage results with the corresponding PL/SQL files. The best part? You won’t need to define any complex object-file mapping rules in the utPLSQL-cli.

By leveraging these properties, is much easier to integrate the utPLSQL reports into your SonarQube analysis pipeline. More information is available in the documentation.

Install/update instructions

  • Download the sonar-zpa-plugin-3.5.1.jar and copy it to the SONARQUBE_HOME/extensions/plugins.
  • Remove the older plugin from that directory.
  • Restart the SonarQube instance.

For custom plugin developers

Binary compatibility is not guaranteed either in between any version number change. Custom plugins should be recompiled against the same version of sonar-zpa-plugin.

Download the zpa-toolkit-3.5.1.jar (requires Java 11+) to test the parser and view the AST.

Full changelog

🐛 Fixes

  • 2334bb8 Correct coverage import for package bodies declared in same file as package spec

🧰 Tasks

  • eb0d9cc Update changelog template

🛠 Build

Assets 5
Loading