CODEWITHSUNDEEP
mavensonarqubecoberturasonarqube5.1sonarqube-scan
MisterStrickland
MisterStrickland

Reputation: 1007

SonarQube: Coverage on New Code never calculated

I have set up SonarQube, Maven and Cobertura to upload unit test coverage at every build run. I want to use the differential views to get coverage for the delta (new code only).

The coverage itself is successfully uploaded, and I can see the delta in lines of code. However, I can't get the "Coverage on new Code" to work.

I tried different values for the leak period, including previous_analysis and previous_version (changing the version from 1.0 to 1.1 in the new analysis). I also used -Dsonar.projectDate to simulate a past date of analysis but still no luck.

Any thoughts?

enter image description here

Upvotes: 6

Views: 15669

Answers (3)

Nerunja
Nerunja

Reputation: 9

Adding this sonar.java.binaries=classes directory, most likely target/classes helped me in fixing this issue. No JaCoCo analysis of project coverage can be done since there is no class files

Upvotes: 1

Lokesh Kumar Bandi
Lokesh Kumar Bandi

Reputation: 11

"Coverage on New Code" is only displayed if you are using/activating SCM support (SVN, Git, ...).

sonar.scm.disabled=false

Upvotes: 1

Nicolas B.
Nicolas B.

Reputation: 7331

The key requirement to obtain new_code -related information/metrics is to leverage SonarQube SCM integration. And to benefit from that you have to install a compatible SCM Plugin applicable to your project (e.g. Git Plugin, SVN Plugin etc.).

Upvotes: 7

Related Questions