Performing various analysis scope adjustments for your project

Check also the language pages for specific language properties related to analysis scope adjustment.

Adjusting the secret detection scope

By default, SonarQube Community Build detects exposed secrets in all files processed by the language analyzers. You can refine the scope of the secret detection: see Adjusting the secret detection scope.

Excluding files over a certain size

You can set the sonar.filesize.limit and sonar.javascript.maxFileSize properties on the CI/CD host to exclude files over a certain limit. For more information, see Analysis parameters. 

Disabling the SCM’s file ignore patterns

Your SonarQube analysis will automatically exclude files that are ignored by your source code control system. For example, in git repositories, it respects the .gitignore file. SonarQube also respects the ignore directives used in SVN repositories.

You can disable this behavior by setting the sonar property sonar.scm.exclusions.disabled to true on the CI/CD host. For more information, see Analysis parameters. 

Related pages

• Excluding specific files from your project's code coverage analysis or duplication check
• Excluding files from your project analysis based on path-matching patterns
• Excluding files from your project analysis based on file extension
• Applying advanced exclusions to your project analysis
• Setting the initial scope of your project
• Verifying the analysis scope of your project
• Adjusting the analysis scope at the global level