Full documentation for SonarQube has moved to a new location: http://docs.sonarqube.org/display/SONAR

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 116 Next »

In Greater Detail

Overview

The Quality Profiles service is the heart of SonarQube, since it is where you define your requirements by defining sets of coding rules (ex: Methods must not have a complexity greater than 10).

Ideally, all projects will be measured with the same profile for any given language, but that's not always practical. For instance, you may find that:

  • Technological implementation differs from one application to another (for example, different coding rules may apply when building threaded or non-threaded Java applications).
  • You want to ensure stronger requirements on some of your applications (internal frameworks for example).
  • Etc.

Which is why you can define as many quality profiles as you wish. To manage quality profiles, go to Quality Profiles (top bar), where you'll find profiles grouped by language:

Each language must have a default profile (marked with a green check). Projects that are not explicitly associated with a specific profile, and which do not have a sonar.profile analysis property will be analyzed using the language's default profile.

Security

The Quality Profiles service can be accessed by any user (even anonymous users). All users can view every aspect of a profile. That means that anyone can see which rules are included in a profile, and which ones have been left out, see how a profile has changed over time, and compare the rules in any two profiles.

To make rule profile changes (create, edit or delete) users must be granted the Administer Quality Profiles and Gates permission.

A project administrator can choose which profiles his project is associated with. See Project Administration for more.

 

  • No labels