Help or NFR: Better way to deactivate rules that are active in SonarWay profiles

[Colin]

@andrew-garland

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.

You can compare rules directly in the UI, if you weren’t aware. Cleverly you can activate rules right from that interface.

Yes, it’s still rather manual.

@andrew-garland

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.

The thinking is that a parent profile is a starting point; the minimum acceptable standard and on top of that you would add rules.

@andrew-garland

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.

Don’t touch the database. And, I’m pretty sure it would get undone at every restart of your SonarQube server.

For what it’s worth we’ve thought about it and the topic isn’t dead entirely. You can add to this topic and I’ll pass your feedback on through the mechanisms we have internally.