We have around 700+ projects being scanned in SonarQube. Most of the projects have configuration, html files that doesn’t and will not have any unit tests but are scanned by SonarQube which results in wrong coverage%. Is there a way to setup or exclude these type of files from the scan? We would like to set it in a way that it works for all 700+ projects.
In Administration → Configuration → General Settings → Analysis Scope, you can configure global file and coverage exclusions. Here’s the documentation link. Hope this helps!
Thank you!!
I was able to find the field under Analysis Scope, What happens to the scan of the repository that doesn’t have these configuration files? Will adding config files using wildcard to analysis scope impact scans of the project that doesn’t have configuration files in the repository?
I can’t say for certain since we’re not utilizing these settings on our SonarQube instance, but I’d assume that projects that don’t contain files matching the exclusion wildcards wouldn’t be impacted.