Apologies for the inconvenience. Yes, we did publish a bug-fix version (v1.6.1) of the extension yesterday that embedded a newer version of the Scanner for MSBuild. Unfortunately, it’s not possible in an Azure DevOps pipeline to specify a particular version of a task; we’ll have to publish a new version of the extension that contains a fix or reverts back to the older version of the Scanner for MSBuild.
The new version of the extension worked on the multiple different configurations we tested it on. Could you provide us with some more information to help us work out why the coverage files are not being converted in your build please?
- please provide the debug output for that section of the “Run Code Analysis” task. The easiest way to get the debug output is to run the build definition with system.debug=true.
- are you using a Microsoft-hosted agent or a self-hosted agent? If Microsoft-hosted, which agent pool?
- which code coverage tool are you using?
- are you building .NET Fx or .NET Core projects, and are you running the tests using “dotnet test” or the VSTest task? If you are using the .VSTest task, which Test Platform Version are you targeting?
FYI the process for converting the .coverage files hasn’t changed. The only difference is that the “Run Code Analysis” task is now looking in a secondary location for coverage files if it did not find any coverage files in the normal location.
Looking at the log output, the task didn’t find the coverage using the previous mechanism so it’s searching the secondary location and finding a coverage file there. I don’t understand how the build would have been able to show coverage in SonarCloud previously if it wasn’t finding a coverage file using the original search method. Are you explicitly passing additional parameters to the “Prepare analysis” task to configure the location of the tests reports, and if so what parameters are you passing?