We have a project that shows in the billing that it has more than 33k LoC
But when jumping into the project detail, we only have 1 long-lived branch (master) and it doesn’t contains any code
We have a project that shows in the billing that it has more than 33k LoC
But when jumping into the project detail, we only have 1 long-lived branch (master) and it doesn’t contains any code
Hi,
What shows up under Measures?
Thx,
Ann
Hi,
Sorry for the delay in replying.
The Measures Overview is empty, I presume. What shows up under Size?
Thx,
Ann
Hi,
Thanks for checking.
I’m now officially out of my depth. I’m going to flag this for more expert eyes.
Ann
Hi @asd_asdasd Sorry for the delay
Can you let me know from what page is your first screenshot?
Also can you send a screenshot of the summary page including the left navigation menu and if there is any line of code per language split, similar to the below screenshot
I cannot find it @dejan.milisavljevic
Thanks. I see you have 34 branches on the left navigation menu. I suspect there is at least one long-lived branch which was scanned before the exclusions were set/changed, and that branch has code inside it. Can you please check that?
I now see that you already said in your initial post that you only have 1 long lived branch. Sorry about that.
I was able to reproduce the issue. When all the files are excluded from the analysis scope, the billing part is not updated. May I ask what is your intent by excluding all the files from the analysis?
We integrate Sonar into the pipeline to ensure it affects all repositories. However, this particular repository is only used for running tests, so we’ve determined that there’s no need to scan it with Sonar, and then we exclude all the files from the analysis.
Hi @asd_asdasd
i have created an internal ticket to update the line of codes even if it reaches 0. In the meantime, you can maybe add a very small file to be scanned and decrease the lines of code.
Hi,
Why keep the project on SonarCloud at all if there’s nothing in it you want analyzed? Why not just delete it?
Ann
Our pipeline automatically creates a new project if it doesn’t exist