Issues not related with new code are considered in quality profile/quality gate after plugin upgrade

SonarQube Community Build, v9.9.8

I have an issue in which, after upgrading a plugin with some new rules, in the new code analysis, in addition to the new code, the whole codebase is scanned, and issues not related to the new code are considered inside the new code quality profile.

Is this behaviour expected?

Thank you very much in advance

Hi,

Welcome to the community!

Only the latest version of SonarQube Community Build is considered active, so you’ll need to upgrade and see if the situation is still replicable before we can help you.

Your upgrade path is:

9.9.8 → 24.12 → 25.7

You may find these resources helpful:

If you have questions about upgrading, feel free to open a new thread for that here.

Regarding your question, you should probably ping the maintainers of your new plugin.

 
Ann