SonarQube: profile inheritance and deactivation of rules

Question

I read the documents on profile inheritance [1] . They say that "a rule inherited from a parent cannot be deactivated." Is this intentional and will it be supported in the future?

When I update some plugin (ie JavaScript analysis plugin), new rules appear, and I need to restore the built-in "Sonar Way" profile to get the new rules. However, when I do this, I lose all previous configurations (deactivated rules), and I must remember what I did in the past, and repeat it again.

Answer 1

It looks like you are using the built-in profile as the default profile. If you are happy with the built-in as-is profile, then this is a great way. But it seems not. So instead, I suggest you make a copy of Sonar Way, I will call it “Copy” and set it up as your default profile. Then after each update, you can reset Sonar Way to use the comparison service to see the differences between Copy and Sonar Way, and then choose which new changes will be applied to Copy.