Skip to content

Configure SonarCloud CI-Based Analysis #431

@seansica

Description

@seansica

Purpose

Branch analysis (analysis of non-pull request branches other than the main branch) is not supported by Automatic Analysis. Therefore, we must switch to using CI-based Analysis in order for the develop branch (et al.) to be analyzed.

Overview

With the CI-based method, the analysis of the code does not take place in SonarCloud itself, as it does with automatic analysis, but in your build environment (either on a local machine or in a cloud CI), each time you make a change and rebuild your project. The analysis is done by a separate tool, called a scanner, that is run in your build environment. The results of the analysis are then sent up to the SonarCloud server, processed and displayed in the SonarCloud web interface.

Analysis parameters can be set in a configuration file within your project. The file used depends on your setup:

TODO

  • Install the Sonar Scanner in the CI runner environment.
  • Configure the sonar-project.properties file with the intended analysis parameters.

Resources

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions