Scanner finding new issues when code hasn't changed

SonarQube Cloud
4

Hey there.

Thanks for raising the feedback! I think what you’re experiencing is normal, and I’ll explain why:

  • The built-in (default) Sonar Way Quality Profiles can change as we add additional rules to SonarCloud. This results in new issues being raised on your overall code, even if the code is unchanged.
  • Rules can become smarter, raising issues that were “false-negatives” before.
  • The scope of rules can change, applying to files they didn’t apply to before (supporting new versions of a programming language, or enabling rules for test code

Luckily, when any of these three things happen, issues are backdated to keep them out of your New Code Period.

Following a Clean as You Code approach, this shouldn’t normally break your Quality Gates.

1 Like