Open gheo21 opened 6 years ago
Hello @gheo21, by chance are you running the analysis from a Wiindows machine ?
Hello,
@BalmungSan no, it 's a macOs. I've already checked the other items related to the test coverage not being shown, but I couldn't find a fix it.
Thanks!
Thanks for reporting this issue @gheo21. It is interesting and before I do any digging I was wondering if you had a chance to check the following:
sonar-scanner
?Just as a sidenote, from my understanding of how the projectBaseDir
property works, if you set it sonar will no longer run analysis on your aggregate project, but I can be wrong about this.
Hello @mwz,
Thanks for getting back to me.
unzip multi-module-new.zip
cd multi-module-new/modules
$SONAR_SCANNER_HOME/bin/sonar-scanner -Dsonar.modules=module1,module2 -Dsonar.host.url=http://localhost:80 -Dsonar.projectKey=module1 -Dmodule1.sonar.sources=src/main/scala -Dmodule2.sonar.sources=src/main/scala -Dsonar.scala.scoverage.reportPath=target/scala-2.12/scoverage-report/scoverage.xml
So as an intermediate solution I will go with option two, but I think this should work with the sonar scanner sbt plugin.
Best regards!
Ok, if other plugins are not affected by this, then it's probably got something to do with the way sonar-scala matches paths in the Scoverage reports. I'll have a look into this when I get a minute.
Hello everybody,
I want to use sbt sonar for analyzing projects. However, the plugin is not able to pick up the scoverage information and display it in sonar for my sbt project. There is one caveat, I have a multi module build and all of my modules are in a subfolder called modules. (Please find attached sample project which is reproducing the error https://github.com/mwz/sbt-sonar/files/2335828/multi-module-new.zip)
I essentially changed the sample project from here https://github.com/mwz/sbt-sonar/commit/47126c442d1cdee40738a03361864d89f4b0ca8a and moved all the submodules in the submodule folder.
I'm running the sonnar scanner
Not producing any coverage information in sonar, just producing the warning:
Running it on the subproject does not make any difference:
Note: Using the docker sonar image sonarqube:6.7.5-alpine via docker compose up. (from here https://github.com/mwz/sonar-scala-docker)