Sonar analysis is showing some wrong analysis on sonarcloud

[AmGupta (Amit Gupta)]

In sonar cloud, the overall code coverage is showing as zero percent when we check it from measures. Is it an intermittent issue. Please let us know and what steps we need to take to correct this or find potential issue.

We are using azure devops pipeline to scan with sonarcloud. can it be associated with version of java used for analysis.

Please let me know what we can do to remediate as even after adding lines of code to increase coverage. It is still showing zero coverage for some files in the code even though it used to display it correctly previously.

[Colin]

@AmGupta

We are using azure devops pipeline to scan with sonarcloud. can it be associated with version of java used for analysis.

No, but you should still upgrade!

@AmGupta

In sonar cloud, the overall code coverage is showing as zero percent when we check it from measures. Is it an intermittent issue. Please let us know and what steps we need to take to correct this or find potential issue.

What do the logs say about the import of code coverage?

How to find logs about importing code coverage

When coverage data isn’t appearing as expected in SonarQube Server / Community Build or SonarQube Cloud, the first place you should look is the scanner logs. Where do I find the scanner logs? This will likely be broken out into its own guide soon The Scanner logs are the output of executing one of the scanners, either directly or wrapped by one of many integrations, such as the SonarScanner for Jenkins, SonarScanner for Azure DevOps, SonarQube/SonarCloud GitHub Actions or SonarQube /…

Do the logs look different depending on whether the build produced a “real” code coverage statistic, versus when it shows 0?