When I configured in Gradle file modules with these properties at the very beginning, all files were scanned. But since I needed to include all the modules in the report, I moved them to the gradle root
Yes, that’s right, let me remind you that when I declared sonarqube and its properties in the garadle module, it scanned Kotlin, and when I brought it to root, it stopped transferring log.txt (7.1 MB)
sonar debug.txt (1.5 MB)
there are difficulties with gradle sonarqube --debug, there are a lot of logs, when running on Jenkins the browser crashes when you view them, and locally if you run it shows only the last part, the logs don’t look informative
We use SonarQube (with it’s Gradle plugin) in a multi module (150+) Android project (with one Android app module and a mix of many Android-library and Kotlin-only modules). We use custom convention plugins to set up each module properly. In these convention plugins we apply SonarQube plugin per module and set the required properties.
This is working fine. So you should consider moving to a similar approach.
Yeah sure. You still need to apply the plugin to the root project and set the projectKey, token etc. there. In your submodules you then also apply the plugin but only set your exclusions, reportPaths, sonar.tests path and so on.