New code coverage not shown in sonarqube dashboard

2,238 views
Skip to first unread message

mahes...@gmail.com

unread,
Sep 11, 2017, 11:57:58 AM9/11/17
to SonarQube
Hi All , 

I am using sonarqube version 5.4 and jacoco version 0.7.9 , jenkins version is 1.611. With upgraded plugin on git and github. But not able to view new code coverage on sonar dashboard.

Currently we are able to view latest bug , code complexity and latest duplication in code, total code coverage . Only issue is Newly added line coverage is showing  "-" .   

Please share steps for integrating sonarqube for java projects to support new code coverage analysis.Let me know if any plugins need to upgrade. 

Thanks for your help here . 

Thanks , 
Mahesh 

G. Ann Campbell

unread,
Sep 12, 2017, 3:16:15 AM9/12/17
to SonarQube
Hi Mahesh,

The current version is 6.5, and the current LTS is 5.6.6. You're going to have a hard time finding help with versions earlier than that. 


Ann

Mark Gortzak

unread,
Sep 12, 2017, 5:30:01 AM9/12/17
to SonarQube
Hi,

Do you have SCM blame enabled (and working)? Code coverage on new code needs to know which lines are new, it uses the SCM blame functionality for that. This was the problem for us (SonarQube 5.6.5).

Greetings,
Mark

Op maandag 11 september 2017 17:57:58 UTC+2 schreef mahes...@gmail.com:

mahes...@gmail.com

unread,
Sep 13, 2017, 2:05:06 AM9/13/17
to SonarQube
Hi Mark , 

Yes we have SCM flag in sonarqube config sonar.scm.disabled=false , and it is working correct to fetch latest code information. 
But its not working for only latest code coverage . 

Not sure is it bug of sonarqube 5.4 , we have also tried it for sonar 6.0 and sonar 6.5 same issue occured ? 

Thanks ,
Mahesh 

shashank...@gmail.com

unread,
Sep 17, 2017, 8:37:15 AM9/17/17
to SonarQube
hi ann,


same sort of issue we are facing in sonarqube6.5. 



thanks,
shashank

Mark Gortzak

unread,
Sep 18, 2017, 1:58:39 AM9/18/17
to SonarQube
Hi Mahesh,

Adding this to the SONAR_SCANNER_OPTS worked for me:
-Dsvnkit.http.methods=Basic,Digest,Negotiate,NTLM

And in a Jenkinsfile:
stage('SonarQube analysis') {
withSonarQubeEnv('SONARQUBE') {
withEnv(['SONAR_SCANNER_OPTS=-Dsvnkit.http.methods=Basic,Digest,Negotiate,NTLM']) {

}
}
}

Hope this helps.

Greetings,
Mark

Op woensdag 13 september 2017 08:05:06 UTC+2 schreef mahes...@gmail.com:

Mark Gortzak

unread,
Sep 18, 2017, 3:12:36 AM9/18/17
to SonarQube
Hi Shashank,

Please reply all for posterity :-).

HI Mark,

Thanks for your reply.
 
I want to know above mention configuration is for git scm. as we are using git for code management.

No. Althought I do not know the internal of Git, I doubt that it uses svnkit internally :-).

Greetings,
Mark



Op maandag 18 september 2017 07:58:39 UTC+2 schreef Mark Gortzak:
Reply all
Reply to author
Forward
0 new messages