Other analysis scope adjustments

Additional analysis scope adjustments can be made in SonarQube Cloud for a few scenerios.

See Supported languages page for language-specific properties related to analysis scope adjustment.

Adjusting the secret detection scope

By default, SonarQube Cloud detects exposed secrets in all files processed by the language analyzers. You can refine the scope of the secret detection, see Secrets for more details.

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

• Setting initial scope

• Excluding from coverage or duplication

• Excluding based on path-matching patterns

• Excluding based on file extension

• Verifying analysis scope

• Introduction to Adjusting the analysis scope at the organization level