SonarQube Code Coverage always shows 0%

[chinnu_yallapalli]

Hello Team,
We have integrated Azure Devops with SonarQube which are Java Applications building from Azure pipelines. We are using Jfrog Maven task to build shared libraries, publising artifacts to Jfrog Artifactory & scanning code from SonarQube by using “Prepare analysis on SonarQube, Run code Analysis, publish Quality Gate Results”. Everything working fine. But only issue is code coverage is 0% for all the applications. So i have tried to install Jacoco plugin from POM.XML, it got istalled successfully by using below code. But still it is showing 0% coverage. Am i missing any Configurations ? Can any one help on this ?
Code :

    <build>
        <plugins>
            <plugin>
                <groupId>org.jacoco</groupId>
                <artifactId>jacoco-maven-plugin</artifactId>
                <version>0.8.10</version>
                <executions>
                    <execution>
                        <goals>
                            <goal>prepare-agent</goal>
                        </goals>
                    </execution>
                    <!-- attached to Maven test phase -->
                    <execution>
                        <id>report</id>
                        <phase>test</phase>
                        <goals>
                            <goal>report</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>    

SonarQube Version : Enterprize Edition: 9.9
Thanks in Advance,

Best Regards
Revathi

[Colin]

Hey there.

I think this guide should help you, including the section on Troubleshooting:

[Coverage & Test Data] Importing JaCoCo coverage report in XML format

Importing JaCoCo coverage report in XML format Version 5.12 of our SonarJava analyzer deprecated uses JaCoCo’s binary format (.exec files) to import coverage. This binary format is internal to the JaCoCo project, and as such there are no guarantees for backward compatibility, so it should not be used for integration purposes. As a replacement, when you scan a project with Sonar scanner, we use a special Jacoco report analyzer, which imports your JaCoCo’s XML coverage report, and this is the pr…

[chinnu_yallapalli]

Hi Colin,
Thanks for the support,
I have tried that above method also but still it’s not generating coverage reports. I can see below messages from logs.
INFO org.jacoco.maven.ReportMojo - Skipping JaCoCo execution due to missing execution data file.
INFO: ‘sonar.coverage.jacoco.xmlReportPaths’ is not defined. Using default locations: target/site/jacoco/jacoco.xml,target/site/jacoco-it/jacoco.xml,build/reports/jacoco/test/jacocoTestReport.xml

I have one more question also we are using Parent child architecture that means do we need to use multi-module builds ? is it causing the issue ?

Thanks in Advance,

Best Regards
Revathi

[Colin]

Hey there.

SonarQube is just responsible for reading reports – not generating them (although we provide some guides that help most users get started).

I would suggest taking SonarQube out of the equation and just making sure you can successfully get a coverage report generated. You can check out JaCoCo’s page on support.