Skip to main content

SonarQube–Error after updating the Prepare Analysis Task in Azure DevOps

I noticed when running a pipeline in Azure DevOps that I got some warnings on the SonarQube related tasks. It complained that I should update to a newer version. So I thought why not and updated the related tasks to the latest version (7.* at the moment of writing this post).

However when I tried to run the pipeline again afterwards it no longer worked and failed on the Prepare Analysis Task:

Starting: Prepare analysis on SonarQube

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

Task : Prepare Analysis Configuration

Description : Prepare SonarQube Server analysis configuration

Version : 7.1.1

Author : sonarsource

Help : [More Information](https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/scanners/sonarqube-extension-for-azure-devops/)

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

##[error][ERROR] SonarQube Server: Error while executing task Prepare: Use 'scannerMode: dotnet' instead of 'scannerMode: MSBuild' in your task configuration.

##[error]Use 'scannerMode: dotnet' instead of 'scannerMode: MSBuild' in your task configuration.

Finishing: Prepare analysis on SonarQube

Turned out that I was a little bit too fast. After changing the tasks to the latest version I also had to explicitly select the way to run the analysis in the Prepare task:

 


After (re)checking the radiobutton and saving the pipeline, the error disappeared.

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more