Using Sonarqube developer edition 8.9 (build 43852)
Sonar scanner 4.6.2
There are a number of rules available which report a large number of issues for us (e.g. java:S6212 reports 16K issues). It is not practical for us to take on a massive effort to clean those out. Also, it is not “fair” in some sense for our code quality metrics today to look worse than they did a month ago because a new rule was introduced.
In a separate ticket, I brought up the idea of simplifying the effort to deactivate problematic rules Help or NFR: Better way to deactivate rules that are active in SonarWay profiles - #4 by Colin_SonarSource
Ideally, though, I would not want to deactivate the rule from the profile, I would simply like a way to have it reported as an issue for pull request analysis/decoration and not for branch analysis. In that way, we can keep the situation from getting worse until we have the time to clean up the technical debt on the main branch. And meanwhile, the overall metrics reported are more appropriate.