We just updated the sonar gradle scanner plugin to latest version
This produced that the
sonarqube task started to spawn several of Gradle processes invoking the task
prepareKotlinBuildScriptModel, from the amount of tasks we see, we strongly believe that this is creating one per module.
Even if this task is fairly fast (~5 seconds), it launches one per module in serial. This means that for a project with 120 modules it increase the total duration by ~10min, which is a big penalty in execution time. We have more modules and this problem literally duplicated our CI checks time.
This is hard to spot at it happens internally in the sonar process and there is no log output, however we have Gradle Enterprise in the project and we noticed thousands of reports from this task from CI (which never happened before with current volume as this is part of the IDE sync). So the only way we have to spot this is thanks to the gradle scans.
I don’t think this is relevant, but just for context: this is an Android project, all in kotlin, in Github, executed in Jenkins, running Sonarcloud.
As a side note, in the release notes was not mentioned anything related to this change. We found out just because lucky we have GE scans and we were able to trace it back to the sonarqube plugin update and see the task reports. I can imagine many people facing big build time increases having hard time to understand why. Is there any where else were we could find the release notes? if not, I would really appreciate sharing more details in them