Scanning Service Fabric solutions in Azure DevOps

[Andrei_Epure]

@Logan_Dam

Firstly I’m not entirely sure how the analyzer is determining what files to scan, unless it detects it from the dotnet restore task. The dotnet build task actually doesn’t build anything with our current solution configuration, because the projects that contain actual code are not set to build in release mode (I am not sure why this is the case, but if I configure them to build in release mode, the analyzer picks up every single source file as a duplicate).

Hello @Logan_Dam, welcome to our community. Apologies for the delay.

@Logan_Dam

Firstly I’m not entirely sure how the analyzer is determining what files to scan, unless it detects it from the dotnet restore task.

The analyzer is a Roslyn analyzer which gets executed during the build by csc.exe (the C# compiler).

@Logan_Dam

    env:
      SONAR_DOTNET_ENABLE_CONCURRENT_EXECUTION: true

This should be in the build step. Anyway, concurrent execution is now turned on by default so you can remove this.

@Logan_Dam

he dotnet build task actually doesn’t build anything with our current solution configuration, because the projects that contain actual code are not set to build in release mode

If they don’t get built, the code won’t be analyzed.

@Logan_Dam

I’m not sure why since I’m using the DevOps task in msbuild mode which works on another project (though that project is not related to service fabric).

The error is raised here.

If the project does not contain MAIN or TEST files … we should log a warning to the user, because no files will be analyzed.

If no code is built, then no files are analyzed. If no files are analyzed, the plugin which pushed the analysis data to SonarQube thinks that it hasn’t been invoked with the correct scanner (because no C# analysis happened).

I hope this helps.