Issue - sonar.coverage.exclusions - not working

SonarQube Server / Community Build
1

We are experiencing issues with the sonar.coverage.exclusions not working on our self-hosted instance of SonarQube and would appreciate your help in determining the cause. I previously encountered similar results, although my implementation was different at that time.

Here are the details of our SonarQube instance:
Server ID: E2A4664A-AYOLQLrW54GJtJ7Fh4Ed
Version: 2025.1.0.102418
Date: 2025-05-30

We have defined sonar.coverage.exclusions at the project level and tried using glob patterns for both files (.js) and folders (**/src/api/wwwroot/). Unfortunately, neither approach has worked, and the quality gate continues to fail as unwanted files are included in the analysis.

We verified that:

  • The settings are not being overwritten by global or command-line (CLI) settings.
  • The settings are being passed to the scanners/sensors.
  • We have reviewed the SonarQube community resources for known issues.

Could you please assist us in identifying why our exclusions are not functioning as expected?

image
image584×230 27 KB

image
image586×197 16.7 KB

image
image586×254 44.1 KB

Thank you.

2

Hi,

Your configured pattern excludes all the files directly under [0-n directories]/src/api/wwwroot. But the file in your second screenshot is not under [0-n directories]/src/api/wwwroot. It’s under [0-n directories]/src/api/wwwroot/js.

The pattern you want is **/src/api/wwwroot/**/*.

 
HTH,
Ann

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.