Skip to main content

SonarQube–The ‘MakeUniqueDir’ task failed unexpectedly

In our efforts to improve the (code) quality of our applications, we started an initiative to get all our teams integrate their projects in SonarQube. We have SonarQube running for a long time inside our organization, but adoption remained fragmented. The initiative turned out quite successful, but as a consequence, we encountered some issues with SonarQube.

Teams started to complain that there build pipelines became flaky and sometimes resulted in errors. The reported error was related to SonarQube and the message was like this:

Error MBS0418: The ‘MakeUniqueDir’ task failed unexpectedly.

System.UnauthorizedAccessException: Access to the path ‘’'db1_work80_sonarqubeout’ is denied.

We found out that the problem was related to our build server setup where we have multiple agents running on the same server. As multiple agents try to execute the ’Prepare Analysis’ task, it sometimes fails with the error message above.

Furher research brought us to the NodeReuse parameter of MSBuild (msbuild.exe -nr:false). Setting this parameter to false don't leave MSBuild.exe processes hanging around (and possibly locking files) after the build completes.

Instead of adapting every build pipeline to pass this parameter, we used the MSBUILDDISABLENODEREUSE=1 environment variable which has the same effect.

Remark: Using this parameter can result in slower builds.

Anyone else who had the same problem?

More information

.NET project | Sonar Documentation

Error MSB4018: The "MakeUniqueDir" task failed unexpectedly - SonarQube Server / Community Build - Sonar Community

MakeUniqueDir task fails intermittently on build agents · Issue #1565 · SonarSource/sonar-scanner-msbuild

msbuild/documentation/wiki/MSBuild-Tips-&-Tricks.md at main · dotnet/msbuild

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

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.

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