The main branch of this project is empty

[DolfM (Dolf Maritz)]

Using SonarQube Analyze v6 in DevOps and Server 10.6

After scan it seems some of the code has not been scanned, the message is displayed on the overview The main branch of this project is empty. Its all c# code and no test code
Core.txt (116.6 KB)

[Colin]

Hey there.

Something definitely seems weird, but I can’t tell what yet. Can you share your full Azure Pipelines (hopefully YML) configuration?

[DolfM (Dolf Maritz)]

I managed to figure it out. I got seriously confused when running the scanner manually vs via devops agent. Looking throughout the log I saw this entry

11:49:19.018 INFO: Importing results from 6 proto files in ‘E:\SQLDATA01_ST01\Agent_work\15.sonarqube\out\0\output-cs’

11:49:19.022 WARN: File ‘F:\Agent_work\15\s\src\MineRP.Core\ViewModels\ValidatingProxy.cs’ referenced by the protobuf 'Met

And I investigated, because the agent was created in the E: path but now there is an F path. And true. E is a mapped path to a mounted device somewhere on our intranet and then F was created as a map to E:\SQLDATA01_ST01, prob to make some other admins work easier.

Although they are both the same

I recreated the agent in F and rerun the analysis task. And all got scanned

So my conclusion is that during the analysis the path does not get resolved and although they do point to the same location they are not the same by string comparison and therefore the location not found