We have many small repos and one major one that is around 300k lines on its own. The admin panel in SonarCloud reports a total of 334k lines. Our maximum number of lines is 500k.
Recently we’ve been attempting to upgrade the sonarqube task version in our ADO pipeline from v2 to v3 in order to access new code analysis updates and remove some warnings from our pipelines. When we moved the major repo task version to SonarCloudPrepare@3, SonarCloudAnalyze@3 and SonarCloudPublish@3, attempting to run these tasks in the CI presents an error:
This analysis will make your organization 'smartr365-1' to reach the maximum allowed lines limit (having 641398 lines). Naturally, such a simple change has not nearly doubled the number of lines in our codebase, so we are confused why this would be the case. Is anyone able to advise? The only other change other than the task number is the necessary change to ‘scannerMode’, from MSBuild to dotnet.
Hi,
Welcome to the community!
In upgrading the task, you’re getting an upgrade of the underlying SonarScanner for .NET. I’m not sure what SS4.NET version you’re coming from with v2 of the ADO task, but current version of the scanner for .NET include the analysis of more languages.
To turn that off, you’ll want to add /d:sonar.scanner.scanAll=false to your begin step, and reanalyze.
HTH,
Ann