Hello there!
I don’t want this to come across as rude, but the Sonar Gradle plugin feels significantly behind the Gradle ecosystem. It honestly seems disconnected from Gradle’s evolution pace — even considering how slowly Gradle itself promotes features from incubating to stable.
Features like configuration cache have been discussed since at least 2020, possibly earlier, and lazy configuration has existed for nearly a decade. Yet configuration cache support is still missing, and many of those threads never received replies.
From the outside, it feels difficult to support these features because the plugin relies on custom implementations instead of Gradle’s standard APIs and patterns. That’s just my personal impression, but it also seems to block adoption of newer Gradle capabilities.
I’ve genuinely considered dropping Sonar for the past five years — not only in personal projects, but across three different companies.
What worries me most is that project isolation is almost here, and Gradle Declarative will require major plugin migrations. Based on the timeline for configuration cache support alone, it’s hard to imagine this plugin supporting Declarative Gradle anytime soon.
This post is mostly about getting clarity. If this situation is not expected to improve in the near future, it would help to know so teams can stop waiting and start moving toward alternative solutions.
Configuration cache and project isolation save a massive amount of build time, especially now that CI systems are processing huge volumes of pull requests generated at AI-assisted speeds.
Sorry for the bluntness, because Sonar itself is a great tool. It just increasingly feels like it does not want to integrate properly with Gradle projects.