# Some exclusions for coverage are not detected

**URL:** <https://community.sonarsource.com/t/some-exclusions-for-coverage-are-not-detected/133581>\
**Category:** SonarQube Server / Community Build\
**Tags:** exclusions, coverage\
**Created:** [January 16, 2025, 7:48pm UTC](https://community.sonarsource.com/t/some-exclusions-for-coverage-are-not-detected/133581 "2025-01-16T19:48:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ricardo\_Emilio\_Borto](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ricardo_emilio_borto/32/45411_2.png) [@Ricardo\_Emilio\_Borto](https://community.sonarsource.com/u/Ricardo_Emilio_Borto)\
**Post date:** [January 16, 2025, 7:48pm UTC](https://community.sonarsource.com/t/some-exclusions-for-coverage-are-not-detected/133581/1 "2025-01-16T19:48:42Z")

</div>

I use “Enterprise Edition 10.7” and we have exceptions configured that are not ignored for coverage. Do you have any recommendations to do?

 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/c/2/c22c3a01d70266e056568154b7fc52f9f23ad7d0.png)  
 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/2/e/2eb728461f5b8cdd351c1cb93632eed2018fca0a.png)  
 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/f/f/ff8a7af41520e3319ed558e2dff57142a7729101.png)

thanks!!

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [January 21, 2025, 9:39am UTC](https://community.sonarsource.com/t/some-exclusions-for-coverage-are-not-detected/133581/2 "2025-01-21T09:39:39Z")

</div>

Hey @Ricardo_Emilio_Borto

If you’re only looking to exclude certain files/directories from **Code Coverage** analysis, make sure you’re setting the right setting. **Source File Exclusions** ignores files that match the pattern completely. If you scroll down a bit, you’ll find the setting for **Coverage Exclusions**

And indeed, I would expect that some of your exclusions work as they’re written (like `src/styles/wirTheme.js`. Have you reanalyzed your project since setting these exclusions, and are you sure that nothing could be overriding these exclusions at the scanner level? Remember that anything you set as `-Dsonar.exclusions=...` will completely override what is set at the server-level ([docs](https://docs.sonarsource.com/sonarqube-server/latest/analyzing-source-code/analysis-parameters/).

You can see what exclusions are taken into account by the scanner in the logs.

```auto
INFO: Indexing files...
INFO: Project configuration:
INFO: Excluded sources: src/styles/wirTheme.js

```

---

<div class="post-metadata">

**Author:** ![Ricardo\_Emilio\_Borto](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ricardo_emilio_borto/32/45411_2.png) [@Ricardo\_Emilio\_Borto](https://community.sonarsource.com/u/Ricardo_Emilio_Borto)\
**Post date:** [January 22, 2025, 2:53pm UTC](https://community.sonarsource.com/t/some-exclusions-for-coverage-are-not-detected/133581/3 "2025-01-22T14:53:48Z")

</div>

Colin! ok! thanks for you recomendations! I check all my deploy process and I found a error with the jenkins pipe exclusions. solved!