Quality Profiles are a core component of SonarQube, since they are where you define sets of rules that when violated should raise issues on your codebase (for example: Methods should not have a cognitive complexity higher than 15). Quality Profiles are defined for individual languages.
To manage quality profiles, browse to the Quality Profiles page where you'll find quality profiles grouped by language.
Ideally, all of your projects will be measured with the same quality profiles, but that is not always practical. In some cases, you may find that:
- You have different technical requirements from one project to another (different rules might apply to a threaded/non-threaded Java application)
- You want to ensure stronger requirements for some of your projects (internal frameworks, for example)
While it's recommended to have as few quality profiles as possible to ensure consistency across projects, you can define as many quality profiles as are necessary to fit your specific needs.
Each language must have a default quality profile (marked with the
DEFAULT tag). Projects that are not explicitly assigned to specific quality profiles will be analyzed using the default quality profiles. There is also at least one built-in quality profile (the Sonar way) per language. These quality profiles are designed by SonarSource with rules that are generally applicable for most projects.
The Sonar way quality profiles are a good starting-point as you begin analyzing code, and they start out as the default quality profiles for each language. That being said, we recommend that you Copy this profile and begin to fine-tune the contents. Why?
- Default quality profiles are not editable, so you won't be able to customize the Sonar way to your needs
- The Sonar way becomes a baseline against which you can track your own quality profiles
- The Sonar way may be updated over time to adjust which rules are included and adjust rule severities.
By default, only users with the Administer Quality Profiles permission can edit quality profiles. But in large organizations, it may not be desirable to grant permissions to change all the quality profiles without distinction. That's why you can also grant users/groups the permission to edit an individual Quality Profile so that, for instance, the management of the Swift profile can be delegated to a group of Swift experts, and the same for COBOL, ...
This delegation of permission can only be performed by someone who already has the Administer Quality Profiles permission or individual edit rights on the profile to which additional permissions should be granted. The interface to grant individual permissions is available on the profile detail page.
Many times people want to work from a profile that's based on a built-in profile without actually using the built-in profile. The easiest thing to do in this case is to go to the original profile, we'll call it Source, in Quality Profiles. From there, click through on the total number of rules in Source to land on the Rules page at a pre-narrowed search of Source's rules. Use Bulk Activate to turn Source's rules on in your target profile.
When SonarQube notices that an analysis was performed with a profile that is different in some way from the previous analysis, a quality profile event is added to the project's event log. To see the changes in a profile, navigate to the profile (Quality Profiles > Profile Name), and choose Changelog. This may help you understand how profile changes impact the issues raised in an analysis.
Additionally, users with quality profile administration privileges are notified by email each time a built-in profile is updated. These updates can be caused by updating SonarQube or updating third-party analyzers.
Use the Back Up feature on the source instance to export the profile to an XML file. Use the Restore Profile feature on the target instance to import the file.
Let's say your company has a minimum set of coding rules that all teams must follow, but you want to add rules that are specific to the technology used in your project. Those rules are good for your team, but irrelevant or even misleading for others. This situation calls for inheritance. Set up a base profile, with your core set of rules. Then create another profile. Once it's created, you can Change parent to inherit from the base profile, then add your missing rules.
Any profile that inherits from another Quality Profile will be updated when the parent Quality Profile is updated.
One profile for each language is marked the default. Barring any other intervention, all projects that use that language will be analyzed with that profile. To have a project analyzed by a non-default profile instead, start from Quality Profiles, and click through on your target profile, then use the projects part of the interface to manage which projects are explicitly assigned to the profile.
Each time a new SonarQube version is released, new rules are added, but they won't appear automatically in your profile unless you're using a built-in profile such as Sonar way.
If you're not using a built-in profile, you can compare your profile to the built-in profile to see what new on-by-default rules you're missing.
Another option is to go to the Rules space, and use the Available Since search facet to see what rules have been added to the platform since the day you upgraded the relevant plugin.
And finally, the profile interface itself will help you be aware of rules added in a new plugin version in the Latest New Rules section on the right of the interface.
Starting from the Quality Profiles page, click through on one of the profiles you'd like to compare, then use the Actions > Compare interface to select the second profile and see the differences.
The Deprecated Rules section of the rules interface itself is your first warning that a profile contains deprecated rules. This pink-background section gives the total number of instances of deprecated rules that are currently active in profiles, and a breakdown of deprecated count per profile. A click-through here takes you to the Rules page to edit the profile in question.
Alternately, you can perform a Rules search for the rules in a profile (either manually or by clicking through from Quality Profiles page) and use the Status rule search facet to narrow the list to the ones that need attention.
The quality profiles can be accessed by any user (even anonymous users). All users can view every aspect of a profile. That means 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 Settings for more.
© 2008-2023, SonarSource S.A, Switzerland. Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution-NonCommercial 3.0 United States License. SONARQUBE is a trademark of SonarSource SA. All other trademarks and copyrights are the property of their respective owners.