New Code Analysis issues in Community Build 25.4

[Anjali_Bhat]

Hi,

We have recently upgraded to SonarQube Community Build version 25.4
With this version, we have been observing some deviations while scanning the new code.
After upgrade, the sonar analysis is considering the overall code instead of new code. But if we delete the same branch and re run the analysis, we are able to see the correct results. With this approach we will lose the results of previous analysis and I suppose this is not intended.
Initially the coverage was around 82% now it has been dropped to 70%

Can you please suggest how this can be resolved.

[ganncamp (G Ann Campbell)]

Hi,

Could you provide some more details? Every analysis “considers” all code.

@Anjali_Bhat

if we delete the same branch and re run the analysis, we are able to see the correct results.

If you’re saying that what’s detected as ‘new’ is incorrect the first time through, then that sounds like a problem with the SCM metadata available to analysis.

 
Ann