Verifying analysis scope

Review configured properties and properties identified by the scanner to determine the project's analysis scope.

This section explains how to verify the configured properties and the properties read by the scanner to compute the project’s analysis scope.

Verifying the analysis scope properties configured for the project

This procedure allows you to view the properties configured in the different possible locations on the CI/CD host and in SonarQube Server UI for a given analysis run.

To verify the configured analysis properties for a project:

1. Run the project analysis.

2. The analysis debug logs show which source and test files are indexed for the analysis (the scanner logs out to the place it was invoked from). If the analysis fails with the error File <fileName> can't be indexed twice. Please check that inclusion/exclusion patterns produce disjoint sets for main and test files then it means that the indicated file is defined in your analysis scope as both source (non-test) and test file. In this case, you must correct your analysis scope.

3. You can also verify all the project’s exclusion parameters. To do so, proceed as follows:

   1. Retrieve the project. See Retrieving projects for details.

   2. Go to Project Settings > Background Tasks.

   3. In the list, locate the project run you want to verify and click the three-dot menu in the far right column.

   4. In the contextual menu, select Show SonarScanner Context. The scanner context is shown:

      • The Global server settings section shows the analysis parameters set in the UI at the global level.

      • The Project server settings section shows the analysis parameters set in the UI for the project.

      • The Project scanner properties section shows the analysis parameters set on the CI/CD host.

Any property set on the CI/CD host and identified by the scanner as a sonar property (that means, with a key starting with sonar.) will be listed as a scanner property even if the scanner does not know about it (in that case, the scanner will just ignore the property, and no error will be raised).

In the Global server settings section of the scanner context, the sonar.global.exclusions and sonar.global.test.exclusions are forced global parameters (see Excluding files based on file paths).

Verifying the analysis scope properties read by the scanner

To know which properties the scanner processes during the analysis run:

• In analysis debug logs, search for the Project configuration section as illustrated below (The scanner logs out to the place it was invoked from). The section may show:

  • Excluded sources: exclusion patterns processed by the scanner to compute the source files to be analyzed.

  • Included sources: inclusion patterns processed by the scanner to compute the source files to be analyzed.

  • Excluded tests: exclusion patterns processed by the scanner to compute the test files to be analyzed.

  • Included tests: inclusion patterns processed by the scanner to compute the test files to be analyzed.

Related pages

• Excluding based on path-matching patterns

• Excluding based on file extension

• Excluding from coverage or duplication

• Applying advanced exclusions

• Other adjustments for analysis scope

• Setting initial scope

• Adjusting the analysis scope Introduction