Overview

This p'age provides a simple overview of all SonarQube Cloud's advanced setup configuration options, making it easier to understand and troubleshoot issues.

If you have completed the Getting started with SonarQube Cloud section, you will have encountered the in-product tutorials. The tutorials provide a decision tree that leads you along the correct path through the various configuration options, depending on the details of your project (language, CI, build tools, etc.)

While the tutorials are useful for getting your specific project set up, they don’t give you an overview of all the configuration options.

In this section, we aim to provide such an overview. By understanding the purpose behind the differing configuration variations, you can see the bigger picture and more easily troubleshoot problems better when they arise.

Automatic vs CI-based analysis

When setting up a new project, the first choice you will have to make is between automatic analysis and CI-based analysis. When you import a project, SonarQube Cloud detects whether it is eligible for automatic analysis and, if it is, begins analysis immediately.

Only projects on GitHub and in a subset of languages are eligible for automatic analysis. Additionally, some advanced features, such as branch analysis, monorepo support, and coverage, are not supported with this analysis method. Nevertheless, if your project is eligible and you don’t require any of the unsupported features, automatic analysis is the recommended method to use. See the Automatic analysis page for details.

If automatic analysis is not suitable for your project, you must set up a CI-based analysis.

CI-based analysis

With the CI-based method, the analysis of the code does not take place in SonarQube Cloud 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 SonarQube Cloud server, processed and displayed in the SonarQube Cloud web interface.

For details, see the Overview of integrated CIs page.

Languages

SonarQube Cloud supports analysis of 25 languages.

See the Supported languages page for the list of languages with information about about which SonarQube product supports which language. Search the page list on the Languages page for your language to find language-specific configuration information.

Analysis parameters

Analysis parameters allow you to control many details of how an analysis is performed.

See the Analysis parameters page for details.

Analysis scope

You can exclude files in your project from analysis by specifying a pattern against which files and directory names are matched.

See the pages about Adjusting analysis scope for details.

Monorepo support

SonarQube Cloud supports the monorepo strategy where multiple separate projects are stored in a single repository.

See theMonorepo support page for details.

SonarQube for IDE

SonarQube Cloud can be connected directly to your IDE using SonarQube for IDE connected mode.

See the SonarQube for IDE page for details about connected mode.

User accounts

SonarQube Cloud allows you to manage your user account easily.

See the pages in the Managing your account section for details.

Webhooks

SonarQube Cloud supports configuration of Webhooks, allowing you to send automatic notifications to external services of analysis activity in your SonarQube Cloud account.

See the page about Webhooks for details.