Your analysis configuration screenshot shows that you've pointed SonarQube Scanner to a .sln
file as the location of your project's source code. Since there's no actual code in the .sln
itself... that would be your problem. The analysis is running and "pushing" results into SonarQube, but those results are empty because no code is found during the analysis.
Then there's the fact that you're trying to analyze a .NET project with the SonarQube Scanner. That used to be the recommended way of doing it, but it required a lot of configuration on your part and it was nearly impossible to get all the t's crossed and i's dotted. So SonarQube Scanner for MSBuild was introduced to relieve you of that burden.
To use SonarQube Scanner for MSBuild, you need to run 3 separate commands, and I suspect using a command line approach is going to be easiest (but I've never used TeamCity, so there could be some feature I'm unaware of to handle SonarQube Scanner for MSBuild analysis).
Here's a link to the docs, but in short what you need to do is
- make sure the SonarQube Scanner for MSBuild is available to your analysis job
- run
MSBuild.SonarQube.Runner.exe begin /k:"sonarqube_project_key" /n:"sonarqube_project_name" /v:"sonarqube_project_version"
- do your normal build
- run
MSBuild.SonarQube.Runner.exe end