What are your scan settings, and do you have code coverage enabled for this? I seem to remember similar issues in the past when there was an outdated code coverage report involved.
Do you clear out all old build artifacts when building your project?
Hi Chris, Thanks for your query.
I’ve figured out the issue. This is happenning because I’m running the command
“dotnet sonarscanner end /d:sonar.login=”""
multiple times.
Now I’m running these 3 commands serially to test it again. These are not very well documented and thus became new adopters to SonarQube like me will become extremally confused. These are the 3 commands now I’m running and I’m happy with the reports.
dotnet sonarscanner begin /k:"" /d:sonar.login=""
dotnet build
dotnet sonarscanner end /d:sonar.login=""