We recently upgrade SonarQube from 9.9.1 version to next LTA 2025.1 version.
After this upgrade many issues are being reported which were not identified by 9.9.1 version of SonarQube.
Sonar projects where we have this issue are using custom quality profiles(copy of 9.9.1 default profile) and custom Quality gate. These in-use quality profiles are not updated yet.
Request you to let me know the possible reasons of these many issues(300+) being identified .
Hi @rashmi.mamtani,
I believe the issues being detected are likely related to few rules. I’m interested in knowing more about the specific rules and languages involved. Since you are using a custom quality profile that was not updated, it suggests the issues may be due to an evolution of an existing rule or an upgrade of the scanner. When SonarQube Server is upgraded, the rules can sometimes change, resulting in improved detection. Additionally, an upgrade of the scanner itself can also impact how the source code is analyzed and identified.
Without more details on the specific rules and languages impacted, it’s difficult to pinpoint the exact reason for the increase in issues. However, my general assessment is that the upgrade to the new LTS version has likely introduced some rule changes or scanner improvements that are now surfacing problems that were previously undetected with the older version. Reviewing the rules change log would be a good next step to understand the root causes.
Please let me know if you can provide any additional information on the specific rules and languages involved. I’m happy to discuss further and try to help diagnose the reasons for the increased issues.
Thank you @Bachri_Abdel ,
Sonar scan uses quality profiles for CSS, Typescript , XML and HTML .
Custom quality profile is exact copy of sonarway (Sonar version 9.9.1) for these technologies.
Sonar Scanner cli version being used is “sonar-scanner-7.1.0.4889-windows-x64”