# Sonar Scanner analysis Issue

**URL:** <https://community.sonarsource.com/t/sonar-scanner-analysis-issue/58238>\
**Category:** SonarQube Server / Community Build\
**Tags:** sonarqube, scanner\
**Created:** [February 13, 2022, 12:26pm UTC](https://community.sonarsource.com/t/sonar-scanner-analysis-issue/58238 "2022-02-13T12:26:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![akash\_p](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/akash_p/32/28722_2.png) [@akash\_p](https://community.sonarsource.com/u/akash_p)\
**Post date:** [February 13, 2022, 12:26pm UTC](https://community.sonarsource.com/t/sonar-scanner-analysis-issue/58238/1 "2022-02-13T12:26:40Z")

</div>

I have two files named swap.c and fac.c, both placed at under same directory.  
I need to run analysis for fac.c only. However, when i run scanner at base dir with below project properties, both the files are indexed and displayed in UI which is undesireable.

I want ONLY compiled/built code to be considered for analysis

[build wrapper]  
build-wrapper-linux-x86-64 --out-dir bw-output gcc fac.c

[Tool details]

- Sonarqube -9.0
- sonar-scanner-cli-4.6.2.2472-linux
- PostgreSQL 12.9

[sonar-project.properties]  
sonar.projectKey=test2  
sonar.host.url=http://localhost:9000/  
sonar.login=7f47a4085a5c9f9576bf855e8d828989696c2345  
sonar.projectVersion=1.0  
sonar.sources=.  
sonar.cfamily.build-wrapper-output=bw-output  
sonar.sourceEncoding=UTF-8

I have attached sonar-scanner -X logs

[log.txt](https://community.sonarsource.com/uploads/short-url/uxadswAdrVW4qjqN07w9AeFWiWk.txt) (71.3 KB)

Please let me know if my understanding wrong

---

<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:** [February 14, 2022, 1:01pm UTC](https://community.sonarsource.com/t/sonar-scanner-analysis-issue/58238/2 "2022-02-14T13:01:37Z")

</div>

Hey there.

Sounds like you want to [Narrow the Focus](https://docs.sonarqube.org/latest/project-administration/narrowing-the-focus/).

---

<div class="post-metadata">

**Author:** ![akash\_p](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/akash_p/32/28722_2.png) [@akash\_p](https://community.sonarsource.com/u/akash_p)\
**Post date:** [February 14, 2022, 3:53pm UTC](https://community.sonarsource.com/t/sonar-scanner-analysis-issue/58238/3 "2022-02-14T15:53:18Z")

</div>

Hello Colin,

If i have to “Narrow the focus” to avoid unnecessary code to be analyzed, then what role is build wrapper playing ?  
I am under assumption that analysis is directly based on what gets recorded in build wrapper step. In this case only fac.c compilation was recorded in build-wrapper-dump.json  
[build-wrapper.log](https://community.sonarsource.com/uploads/short-url/s8oOUQ5DvpAYripxC0QsN4silKp.log) (15.2 KB)  
[build-wrapper-dump.json](https://community.sonarsource.com/uploads/short-url/4mpQcrAil8AytHYGjlcz7UUy1hv.json) (2.0 KB)

Whereas analysis considers both the files

 ![Capture](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/2/2/225b0a11b635539d8fc9f949fbbf27f3edeae6a0.png)

---

<div class="post-metadata">

**Author:** ![akash\_p](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/akash_p/32/28722_2.png) [@akash\_p](https://community.sonarsource.com/u/akash_p)\
**Post date:** [February 15, 2022, 10:30am UTC](https://community.sonarsource.com/t/sonar-scanner-analysis-issue/58238/4 "2022-02-15T10:30:22Z")

</div>

@Colin / @ganncamp can you comment on the query ?

---

<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:** [February 18, 2022, 9:51am UTC](https://community.sonarsource.com/t/sonar-scanner-analysis-issue/58238/5 "2022-02-18T09:51:50Z")

</div>

Hey there.

The build-wrapper collects necessary information to perform analysis – however, other files captured by `sonar.sources` will still be indexed.