We are using SonarQube version 7.9 and build wrapper for C/C++ version 6.3 on linux environment. We are using git as our SCM.
We have C/C++ project and we would just like to scan C/C++ files that the build wrapper detects. The build wrapper does analyse the files but at the end it seems like the scanner reanalyses all files from git blame. This is not accepted as we have unit tests and other files that we don’t want to scan.
Build wrapper correctly detects and analyses all ~800 files that we want to analyse but the git blame analysis then analyses >2000 files.
- Could you explain what is the difference between these two scans?
- Why is the scanner ignoring build wrapper files and scanning everything?