Once SonarQube has been installed, you are ready to run analyses on your projects.

Scope of Analysis

SonarQubecan perform analysis on 20+ different languages. The outcome of this analysis is going to be mainly quality measures and issues (non-respect of coding rules). However, what gets analyzed will vary depending on the language analyzed:

• On all languages, a static analysis of source code is performed (java files, Cobol programs, etc.)
• A static analysis of compiled code can be performed for certain languages (.class files or jars in Java, dll files in C#, etc.)
• A dynamic analysis of code can be performed on certain languages (execution of unit tests in Java, C#, etc.)

Running Analysis

First, you should install the language of the project to be analyzed either by a direct download or through the update center.

To launch an analysis, the following clients are available:

• Analyzing with SonarQube Runner (recommended client)
• Analyzing with SonarQube Ant Task
• Analyzing with Maven
• Analyzing with Gradle
• CI Engines

For more information, see also:

• Analysis Parameters
• Project Examples

Since SonarQube3.3, it is possible to analyze a multi-module project with different languages. For SonarQubeversions prior to 3.3, each of those modules needs to be analyzed separately by running a specific analysis. Then the results can be aggregated at project level, using the Views plug-in.