Message-ID: <455894495.94841.1397946566035.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_94840_887284009.1397946566034" ------=_Part_94840_887284009.1397946566034 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Quality Profiles service is the heart of SonarQube, since it is wher= e you define your requirements by defining sets of coding rules (ex: Methods must not have a compl= exity greater than 10).
Ideally, all projects will be measured with the same profile for any giv= en language, but that's not always practical. For instance, you may find th= at:
Which is why you can define as many quality profiles as you wish. T= o 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 associate=
d with a specific profile, and which do not have a
sonar.profile analysis property wil=
l be analyzed using the language's default profile.
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 anyo= ne can see which rules are inc= luded in a profile, and which ones have been left out, see how a profile has changed over time, and compare the rul= es in any two profiles.
To make rule profile changes (create, edit or delete) users must be gran= ted the Administer Quality Profiles and Gates per= mission.
A project ad= ministrator can choose which profiles his project is associat= ed with. See Project= Administration for more.