Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure SonarCloud CI-Based Analysis #431

Closed
2 tasks
seansica opened this issue May 23, 2023 · 0 comments
Closed
2 tasks

Configure SonarCloud CI-Based Analysis #431

seansica opened this issue May 23, 2023 · 0 comments
Assignees

Comments

@seansica
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant