I’m using a SonarQube task within a build pipeline with Azure DevOps. The only project being built as part of that pipeline is a .NET Core 3.1 one. The problem is that the SonarQube task always fails with “No analysable projects were found. SonarQube analysis will not be performed. Check the build summary report for details”.
From what I’ve seen, the usual culprit is the missing project guid within the .csproj file, as reported here, however in this case I made sure to copy the project guid from the solution’s .sln file. Yet the error is still there.
I have other Azure DevOps build pipelines that share the same template as the one described above. A variable within controls the path of the project to be built as part of the solution. For some reason all of the other projects (also .NET Core 3.1) can be analyzed just fine by SonarQube, and it’s only this one project that’s generating the “no analysable projects were found”. I’ve double-checked that the path to the project used for the build is correct.
I’ve also taken the logs from the SonarQube server (log level is set to INFO currently), but couldn’t find anything related to the error.
I’m running SonarQube v4.17.0.
Is there anything else that I should check, or any other place that could yield the cause of the problem?