Hi team,
We are running SonarQube server 9.9 LTS and we are planning to upgrade to 10.6. We have STG environment where the new version is deployed and I started some testing. One of the first thing I did was to scan one project main branch which use custom quality profile. The custom profile has some disabled rules, compared to the SonarWay one. Unfortunately when the scan had finished I noticed that the QP has been reverted from the custom one to the default one and a message saying: Upgrade to SonarQube 10.6.0.92116 has updated your Quality Profiles. Issues on your project may have been affected.
In the details in the activity log I can see:
First analysis since upgrading to SonarQube 10.6.0.92116
Issue Detection:Capabilities have been updated (Java)
Issue Detection:Capabilities have been updated (XML)
Quality Profile:Stop using “CUSTOM” (Java)
Quality Profile:Stop using “CUSTOM” (XML)
Quality Profile:Use “Sonar way” (Java)
Quality Profile:Use “Sonar way” (XML)
New analysis:+0 Issues•-10.9% Coverage
Can you help me troubleshoot this, and if possible to prevent this QP revert on other projects.
The SQ version is 10.6 Data Center Edition and for scanning this project I used maven scanner 3.9.1.2184.
In the Jenkins log, everything is like before and no errors or warnings are shown there.
The configuration, on high-level, of the custom QP can be seen bellow(I have masked some of the company related things):
