Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Infoiframe
iconframeborderfalse0
titleheightTable of Contents10

Table of Contents
maxLevel2

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

Scope of Analysis

SonarQube can perform analysis on 25+ different languages. The outcome of this analysis will be quality measures and issues (instances where coding rules were broken). However, what gets analyzed will vary depending on the language:

  • 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 plugin(s) for the language(s) of the project to be analyzed, either by a direct download or through the update center.

Then, there are two ways to add a new project to your SonarQube instance. Either:

  • You can analyze it first with the default parameters and then configure it (define permissions, set quality profiles, etc.).
  • Or you can provision it. This will allow you to configure it prior to running the first analysis.

To run an analysis, the following methods are available:

For more information, see also:

srchttp://redirect.sonarsource.com/doc/analyzing-source-code.html

Documentation has been moved to http://redirect.sonarsource.com/doc/analyzing-source-code.html.

Documentation has been moved to http://redirect.sonarsource.com/doc/analyzing-source-code.html.