Sonar issues spiked from 0 to 2k with same code base

[raks05 (Rakshita Singh)]

Hi Team,

We are observing a sudden spike in Sonar issues in our project.

Details:

• Previously reported issues: 0

• Current reported issues: ~2000

• Codebase: No major changes

• Branch: Release_March_18.0.0( it is a clone of Release_February_17.0.0, but there were no code changes)

• SonarQube / SonarCloud Version:

  C:\sonarqube-10.6.0.92116\sonarqube-10.6.0.92116

• CI/CD Tool: Azure DevOps

Concern:

The codebase has not significantly changed, but the number of issues suddenly increased from 0 to around 2000 after the latest analysis.

Questions:

1. What could cause such a sudden spike without major code changes?

2. How can we identify what exactly caused this increase?

Please let us know how we can investigate the root cause.

Thank you.
March_Feb_Difference

[jilles-sg (Jilles Tjoelker)]

The “Lines of Code” before the change is nothing, which suggests a problem has been fixed that prevented analysis. For example, it could be that an incorrect exclusion matched everything or that all code was incorrectly recognized as test code (which is scanned using a limited set of rules and does not count lines of code).