'Generic Coverage Report' skipped because of missing configuration requirements. Accessed configurat

SonarQube Server / Community Build
, ,
1

As I had setup the sonarqube for coverage report which will be generated by the jacoco and then it will fetched by sonarqube by the help of this

mvn -X $MAVEN_CLI_OPTS $SONAR_MAVEN_PLUGIN:sonar -Psonar -Dsonar.host.url=$SONAR_HOST_URL -Dsonar.token=$SONAR_TOKEN -Dsonar.projectKey="$SONAR_PROJECT" -Dsonar.coverage.jacoco.xmlReportPaths=$Jacoco_pwd/microservice/target/site/jacoco/jacoco.xml -Dsonar.projectName="$PROJECT_NAME" -Dsonar.qualitygate.wait=$WAIT_FOR_CODE_SCAN -Dsonar.qualitygate.timeout=$CODE_SCAN_TIMEOUT

all paths and report are generating, but at last it is giving log likewise

‘Generic Coverage Report’ skipped because of missing configuration requirements.
Accessed configuration:

  • sonar.coverageReportPaths:

and when I’m went to sonarqube server then it is showing Not Computed 66.5% estimated after merge in my feature branch sonarqube ui, I have hitted the sonar server from my local then coverage is looking good to me, but in gitlab this generic Coverage Report is coming…

Do let me know if you need anything else from my side.

2

Hi,

Welcome to the community!

I think this is unrelated to your coverage stats in SonarQube since you don’t seem to be passing in a generic coverage report.

Is this really a branch analysis or a PR analysis? The “after merge” part makes it sound like a PR, which is limited to analysis of only what changed in the PR. And if there were no code changes in the PR (i.e. only comments, whitespace or configuration) then it’s quite normal for coverage to be irrelevant and thus not computed.

 
HTH,
Ann

3

Yes, this is a PR analysis, can it be possible that Overall coverage report which is in master branch will also reflect in PR and also in PR Sonar Bot, i.e PR will take overall coverage from master branch and after that according to code changes it will decrease/increase X% from that overall coverage either overall coverage should be increased by the new code changes or else i will decreased..

Can this be achieved ??

4

Hi,

PRs report the coverage on what was changed in the PR. You could have 3% coverage overall, but if your 20-line PR had coverage for every line, your PR analysis would show 100% coverage.

There is an “Estimated after merge” value which tries to calculate what the overall coverage will be once the PR has been merged. But it’s not guaranteed to be accurate.

 
HTH,
Ann

5

Okay Got it Thanks for your Support.