The line counter for private projects seems to have changed

SonarQube Cloud
1

Template for a good new topic, formatted with Markdown:

  • ALM used (Azure DevOps)
  • CI system used (Azure DevOps)
  • Azure Devops Task

We have 29 projects, and have been running under 500K lines for a couple of years. The scanner has recently flagged us twice in 2 days that we were at 560K, then 680K.

The project in question only shows about 20K increase in lines (due to a package-lock file)

Something wacky is going on with the line counting. There is no possible way we increased our line count by almost 200K in 2 days. Something has changed in the line counting. It has forced me to upgrade our plan twice in two days.

Is it possible to get help in this situation where it appears to be a Sonar bug that was introduced?

2

Hi,

Welcome to the community!

We haven’t changed how we count lines.

Your best bet for debugging this is to enable debug analysis logging by adding -Dsonar.verbose=true and checking which files are indexed. Before that, though, I would add an exclusion for that package-lock file.

 
HTH,
Ann