Compile only changed modules when running sonar gradle task

[Jun_Park]

I am using sonar gradle task on spring multimodule project

My project consists of many subprojects and as I understand, the sonar plugin adds the sonar task to root project.
Therefore even if I make changes to just one module, the task scans and compiles all subprojects.
The task runs more than 10 minutes and I am looking for ways to reduce the time.

Is there a way to run the sonar task on changed modules only?
A way of targeting modules might also be helpful

[Colin]

Hey there.

You can’t get away with not scanning all projects (although if you’re using Pull Request analysis in Developer Edition, a cache will get used if you’ve scanned the target branch).

You can however choose when you compile. If you’re performing some sort of incremental build and all the bytecode is available by the time the scanner kicks off, this might help:

SonarScanner for Gradle: you can now decide when to compile

Hello, We made a change in the SonarScanner for Gradle so you can control when your code is compiled. Until today, the SonarScanner for Gradle was behaving like this: when you were running gradle sonar, under the hood, it was triggering/forcing the compilation this was a hard dependency and it was not possible to deactivate it We made this design choice years ago because, for Java and Kotlin code, the Sonar analyzers must have access to the bytecode to perform an accurate analysis. So forci…