EDIT [2026-07-09]: We discovered an issue with version 7.2.0, 7.2.1 and 7.2.2 of the scanner and recommend that you keep your project on or downgrade to version 7.1.0.6387. See this post for further details.
We are pleased to announce the release of the SonarScanner for Gradle 7.2.2 which introduces support for the configuration-cache feature of Gradle. Our primary goal for this release was to improve compatibility with new Gradle features, so that they can be enabled in your builds and improve performance.
This release officially supports the configuration-cache feature of Gradle.
If you are using Gradle 9 or looking to optimize your build times, you can now activate the Gradle Configuration Cache on commands that include the sonar task. The configuration cache is the recommended way of running Gradle 9. It is available with versions 8.1 and above.
This means faster sequential runs: when running two sequential Gradle commands with the same tasks and environment, the plugin now utilizes caching, which skips the configuration phase in the second.
For optimal use of the configuration cache: We have refactored the plugin to access only Sonar environment variables and system properties. The file system is no longer accessed during the configuration phase. Note that this also improves how the plugin handles parallel execution. If you use the --parallel flag in your builds, this release reduces the potential for bugs and lock issues.
Should you encounter any issues with this new release, please open a new thread for discussion.
Important compatibility note: Due to a critical issue in Gradle 8.3 (see https://github.com/gradle/gradle/issues/25434), we are officially dropping support for this specific version. Users on Gradle 8.3 are strongly advised to upgrade to versions 8.4–8.14 or 9.0–9.2 to ensure full compatibility and stability with the Sonar Gradle Plugin. Version 7.6.4 is still supported, but we recommend migrating to the newer supported releases where possible.