How do I turn off rules in SonarQube?

How do I turn off rules in SonarQube?

Permanently ignore a rule

1. Go to your organization page, then click on “Quality Profiles”.
2. Scroll to the HTML Quality profile.
3. Once you are on the new Quality Profile page, look at the “Rules” section on the left.
4. Go to your project’s page and click “Administration”->“Quality Profiles”

How do you edit rules in SonarQube?

You can’t modify an existing rule. A workaround is to write a custom rule. However, you should first seriously consider whether the behavior you want to achieve is really specific to your own environment. If that’s not the case, you can suggest a change to the existing rule by joining the SonarQube google group.

How do I ignore code coverage in SonarQube?

Ignore Code Coverage You can prevent some files from being taken into account for code coverage by unit tests. To do so, go to Administration > General Settings > Analysis Scope > Code Coverage and set the Coverage Exclusions property.

Where are rules defined in SonarQube?

By default, when entering the top menu item “Rules”, you will see all the available rules installed on your SonarQube instance. You have the ability to narrow the selection based on search criteria in the left pane: Language: the language to which a rule applies.

How do you write a rule in SonarQube?

Once your new rule is written, you can add it SonarQube:

1. Login as an Quality Profile Administrator.
2. Go to the Rules page.
3. Select the Language for which you want to create the XPath rule.
4. Tick the Template criterion and select “Show Templates Only”
5. Look for the XPath rule template.

When an issue is automatically closed in SonarQube?

Issues are automatically closed (status: Closed) when: an issue (of any status) has been properly fixed => Resolution: Fixed. an issue no longer exists because the related coding rule has been deactived or is no longer available (ie: plugin has been removed) => Resolution: Removed.

How do you stop sonar issues?

You can put //NOSONAR at the end of the line triggering the warning. For most languages, SonarQube supports the use of the generic mechanism: //NOSONAR at the end of the line of the issue. This will suppress all issues – now and in the future – that might be raised on the line.

How do you create a new rule in SonarQube?

Adding coding rules using Java

1. Create a SonarQube plugin.
2. Put a dependency on the API of the language plugin for which you are writing coding rules.
3. Create as many custom rules as required.
4. Generate the SonarQube plugin (jar file).
5. Place this jar file in the SONARQUBE_HOME/extensions/plugins directory.

How do I fix SonarQube problems?

Issues lifecycle

1. Open – set by SonarQube on new issues.
2. Confirmed – set manually to indicate that the issue is valid.
3. Resolved – set manually to indicate that the next analysis should Close the issue.
4. Reopened – set automatically by SonarQube when a Resolved issue hasn’t actually been corrected.

Is there any way to achieve this using SonarQube?

Using SonarQube, we wish to create a new quality profile from an existing profile, but deactivate a couple of the rules. The GUI allows us to modify the severity of inherited rules, but not deactivate the rules. Is there any way to achieve this?

How to disable sonar rules for specific files?

Is there a way to disable Sonar rules for specific files, and if so, how? Since SonarQube 4.0, you can define issue exclusion patterns based on rule key and file path pattern. On previous versions, you can rely upon the Switch Off Violations plugin. You can annotate a class or a method with SuppressWarnings.

Can you change the root profile in SonarQube?

Because Sonarqube does not allow us to change the root profile, so if you want to modify the rules set, you need your own rules. Last but not least, don’t forget to set your new profile as default. On newer version of SonarQube (mine is 6.7.4):

Why is the squid s00105 rule ignored in sonar?

I tested this quite a lot and finally found that setting common rules (anything that starts with “common-xxxx”) from scanner side (pom, command line etc) will be ignored and it wont work. The language specific rules can be passed line arguments and thats why the “squid:S00105” rule is getting ignored correctly.