This shouldn’t be the case as code smells are supposed to be in code files only not in files generate after build .
Hi,
Are you currently configuring the sonar.sources analysis parameter for this project? This allows you to limit the analysis scope to your code files. Documentation on it can be found here.
Hi @smanning sonar.sources is defined as root directory where build folder is also generated , exclusively only sonar.exclusions parameter is defined for certain files and folder . Previously only code files were included in analysis not build folder , what could be the reason for it’s inclusion .
If your sonar.sources is your root directory, it makes sense that the build folder was analyzed as well. If you want to keep the sonar.sources at its current value, then you could solve your issue by adding your build folder to your exclusions.
Hard to say without knowing much about your project or how your analysis runs. It could be that the build folder didn’t contain scannable files previously or it wasn’t present at the time the analysis ran. 
Hi @smanning , thank you for your response i’ve excluded build folder and coverage report is generating as expected .
1 Like