Code coverage files are not excluded from new multi-language support

SonarQube Server / Community Build
, ,
1

Our code lines quota has been suddenly consumed in the last two weeks due to code coverage files (xml) being considered as code with the new scanAll default.

I would expect scanAll to automatically ignore any files indicated as reports using config such as sonar.cs.opencover.reportsPaths.

The closest issue I can find is: Multi-Language Support: Ignore bin/ and obj/ · Issue #2110 · SonarSource/sonar-scanner-msbuild · GitHub which argues that non-code folders should be ignored.

We don’t gitignore our code coverage folder because it never exists on our local machines.

This is in Gitlab CI/CD, when using the latest dotnet-sonarscanner dotnet tool installed from nuget, and using sonarcloud.

    - dotnet tool run dotnet-sonarscanner begin
      /o:"$SONAR_ORG_KEY"
      /k:"$SONAR_PROJECT_KEY"
      /d:"sonar.token=$SONAR_TOKEN"
      /d:"sonar.host.url=$SONAR_HOST_URL"
      /d:"sonar.qualitygate.wait=true"
      /d:"sonar.cs.opencover.reportsPaths=$CI_PROJECT_DIR/results/**/coverage.opencover.xml"
      /d:"sonar.cs.vstest.reportsPaths=$CI_PROJECT_DIR/results/*.trx"
2

Hi,

Thanks for this report. I’ll make sure the team sees it.

In the meantime, you can address this, as you alluded, by excluding those files.

 
HTH,
Ann

1 Like
4

Hi, @tboby

Hi @cseges,

We just released v8.0.2 of the Scanner for .NET that implements some corrections for coverage files and allows using sonar.exclusions to fine-tune the analyzed files if needed.

Please let us know if this works for your use-case.

Denis.

1 Like