Using * Developer Edition* Version 8.7 (build 41497)
We are trying to customize / tune the rules that ship with SonarQube to fit our needs.
I have seen google results saying that the way to accomplish this is to create a new profile and copy in the rules for SonarWay into it. For me, this is a non-starter. i don’t want to be tied to doing manual diffs of the rules in my copy compared to updates done by sonarqube automatically whenever we upgrade.
I am happy to take advantage of extending the built in profile, and we do that in several cases to change severity or some kind of threshold (like line length or complexity). I don’t see why I can’t just deactivate an inherited rule, as it seems like it would solve my problem without the huge downside of manually copying into a new profile. FWIW, right now, I am forced to do things like setting a threshold extremely high as a workaround to disabling it, but I would prefer to simply disable it (which I assume is also better for performance).
Is there a way to disable a rule by brute force via the DB? I realize it might get undone on upgrade, but IMO this it far less work to re-apply DB changes after each release than trying to do a manual compare of rule set changes if I create a copy.