Code coverage showing as 0% after moving to 9.9 LTS EE

  • SonarQube 9.9 LTS EE, sonar-scanner- ,
  • how is SonarQube deployed: zip
  • Moved from 7.8 Sonarqube to 9.9 SonarQube

We got the staging license and have set up 9.9 LTS EE and configured our projects. Previously, we were using 7.8.
Generally, the sonar analysis is working fine with 9.9. However, it’s showing the coverage as 0.0%

We have configured the sonar.coverage.jacoco.xmlReportPaths and sonar.coverage.exclusions in in our code base correctly since we were seeing some warnings for these properties.

Even after the corrections, the code coverage is still showing as 0%

What do the logs say about code coverage import?

I’m surprised you set sonar.coverage.jacoco.xmlReportPaths in a file, as you should normally be using the SonarScanner for Maven or SonarScanner for Gradle, which have other mechanisms to set analysis parameters.

Hi Colin
We can see the below snippet in the log for all the modules
INFO: Sensor JaCoCo XML Report Importer [jacoco]
INFO: Importing 3 report(s). Turn your logs in debug mode in order to see the exhaustive list.
INFO: Sensor JaCoCo XML Report Importer [jacoco] (done) | time=109ms

We are using the below jenkins jacoco plugin at jenkins side
name=‘Jenkins JaCoCo plugin’ groupId=‘org.jenkins-ci.plugins’ artifactId=‘jacoco’ version=‘3.3.2’

We can see the below in sonarqube 9.9 EE

We can see the coverage details correctly in jenkins

Only issue is it’s showing as 0% in the sonarqube side

Any inputs/guidance would be much appreciated