Project Coverage Measures Crashing

SonarQube Server / Community Build
,
1

I recently SonarQube updated to: Community Edition v10.7 (96327) and am seeing unexpected behavior with the code coverage preview. Our project is setup using a manual CLI configuration, our build server runs: dotnet sonarscanner begin followed by: dotnet build and uses: dotnet-coverage collect "dotnet test" -f xml -o "coverage.xml" to push the code coverage results to sonar scan. Our build process has not changed since we updated to v10.7 however we are no longer able to view the detailed code coverage report in sonar.

On the project overview page, we can see the coverage rate of new code, so the coverage appears to get from our build server to sonar.

328×140 6.47 KB

However, when we click on the link to view the coverage report we are seeing an empty page with the following error:

555×148 5.21 KB

On the page where we used to see coverage details, I am getting a 404 response on a request to: https://sonar.{SITE_NAME}.com/api/measures/component?{URL_ENCODED_QUERIES}

I am also seeing the following error returned on a request to: https://sonar.{SITE_NAME}.com/api/alm_settings/get_binding?project={PROJECT_NAME}

"errors": [
       {
           "msg": "Project \u0027{PROJECT_NAME}\u0027 is not bound to any DevOps Platform"
       }
   ]

How can we correct the above issue on the latest build of sonarqube?
Thanks,

2

Following up on this issue it seems to be related to and issue with the IIS Proxy not passing the request through to the sonar site. I have used the following blog post and sonar docs to configure the IIS proxy. But I don’t see anything indicating why every other part of the site functions, but component_measures requests fail.

Any information would be helpful.
Thanks,

1 Like