Hello Sonar Community,
We have been using SonarCloud for 3+ years, integrated with our organization’s Gitlab repositories on Gitlab.com. We have a limit of 100K lines of code in our plan for SonarCloud. We appear to have temporarily exceeded this limit, but then we removed a stale repository to return below the limit (currently ~98K LOC).
The problem we’re trying to solve is that the SonarCloud analysis on the repository’s master branch is not running correctly. Specifically, when changes are merged to our repository’s master branch, the pipeline runs, but the displayed results are for a commit some 11 months ago, and the analysis says it has failed due the “Number of Lines Exceeded”.
What we have tried/checked already:
-
The total number of lines for our projects is shown in the admin panel as being less than the number of lines allowed for our plan (98k vs 100k).
-
It is possible that at one point our projects exceeded the allowable number of lines, but that is no longer the case.
-
We have cleared the “sensor cache” and rerun, without effect.
-
We have specified sonar.sources=src in our sonar-project.properties file to exclude some large generated files, without effect.
-
If we view “Analysis” → “More” → “Measures” → “Size” → “Lines”, a different, higher line count is displayed, which does indeed exceed the allowable number of lines for our plan. Again, this is a different number of lines than is displayed in other views, such as the admin panel. The difference in line count is roughly equivalent to the line count of the files excluded by the sonar.sources setting
Any suggestions for how to address this problem?
Thank you