Sales pointed me here. We have a legacy license with 1m lines of code. We have about 525k under analysis. I added a new repo with 128k lines of code and it fails to analyze because it says we will exceed 1m. Which is not correct. So how do we get around this?
Anyone in this forum able to help me figure this out?
Hi,
Welcome to the community!
You might want to familiarize yourself with the FAQ, in particular the section on when you can expect a response. 
Regarding your question, it’s a sad fact that the analysis logs don’t indicate how many LOC were found, so these questions are always “fun” to debug.
You say there are only 128k LOC in your new project, but analysis is apparently finding approximately 500k. The first thing to do is look at your analysis scope, because clearly more than you anticipated was picked up. Did you accidentally include library directories? Generated code? What is sonar.sources set to?
It may be helpful to add -Dsonar.scanner.internal.dumpToFile=[path to file] to your analysis command line. Doing so will write the calculated analysis properties to file.
Additionally, can you check your server logs? They may offer some additional information
Ann
Ann
Thank you for your helpful response. I thought my email response last week made it up here but it did not, so I will paste it in below.
Thank you for your help. I was able to get it to scan the repo but had to remove other repos to remain under the limit. Ironically, once it was scanned, it showed 305k lines of code. I still have no idea how it finds that much. But, its in there now and working.
Again, appreciate your guidance here.
1 Like