Skip to main content

Error when running Sonar Cloud on Angular projects

And the story continues…

After setting up Sonar Cloud integration in Azure DevOps and applying a fix for .NET Core applications, I tried to do the same thing for our Angular code.

It didn’t work as expected, this is the output I got:

[More Information](https://sonarcloud.io/documentation/analysis/scan/sonarscanner-for-azure-devops/)

==============================================================================

D:\a\_tasks\SonarCloudPrepare_14d9cde6-c1da-4d55-aa01-2965cd301255\1.12.0\classic-sonar-scanner-msbuild\SonarScanner.MSBuild.exe end

SonarScanner for MSBuild 4.10

Using the .NET Framework version of the Scanner for MSBuild

Post-processing started.

18:04:47.123 Fetching code coverage report information from TFS...

18:04:47.125 Attempting to locate a test results (.trx) file...

18:04:47.64 Looking for TRX files in: D:\a\1\TestResults

18:04:47.64 No test results files found

18:04:48.125 Did not find any binary coverage files in the expected location.

18:04:48.127 Falling back on locating coverage files in the agent temp directory.

18:04:48.128 Searching for coverage files in D:\a\_temp

18:04:48.128 No coverage files found in the agent temp directory.

##[error]The SonarQube MSBuild integration failed: SonarQube was unable to collect the required information about your projects.

Possible causes:

1. The project has not been built - the project must be built in between the begin and end steps

2. An unsupported version of MSBuild has been used to build the project. Currently MSBuild 14.0.25420.1 and higher are supported.

3. The begin, build and end steps have not all been launched from the same folder

4. None of the analyzed projects have a valid ProjectGuid and you have not used a solution (.sln)

The SonarQube MSBuild integration failed: SonarQube was unable to collect the required information about your projects.

Possible causes:

1. The project has not been built - the project must be built in between the begin and end steps

2. An unsupported version of MSBuild has been used to build the project. Currently MSBuild 14.0.25420.1 and higher are supported.

3. The begin, build and end steps have not all been launched from the same folder

4. None of the analyzed projects have a valid ProjectGuid and you have not used a solution (.sln)

Generation of the sonar-properties file failed. Unable to complete SonarQube analysis.

##[error]18:04:48.176 Post-processing failed. Exit code: 1

18:04:48.176 Post-processing failed. Exit code: 1

##[error]The process 'D:\a\_tasks\SonarCloudPrepare_14d9cde6-c1da-4d55-aa01-2965cd301255\1.12.0\classic-sonar-scanner-msbuild\SonarScanner.MSBuild.exe' failed with exit code 1

Finishing: Run Code Analysis

Did you notice my mistake? As I’m building an Angular application, I shouldn’t be using MSBuild. Instead I need to use the stand alone scanner.

Let’s fix this in the Prepare Analysis task:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...