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:

Labels:

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B
Read more

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…
Read more

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.
Read more