The Issue
We saw an issue with our SonarQube 10.3 Developer Edition (that is running as a Docker image hosted in Azure) when it was doing the analysis of a project that included Azure Bicep files.
The Azure DevOps pipeline that triggered the SonarQube analysis was not failing, but within the SonarQube analysis step an …
Read MoreThe Problem
We run our SonarQube instance in a Docker container hosted in an Azure Web App Service. Today, with no notice, it failed. We did the obvious, just tried to restart it and the startup process failed.
Looking at the Azure Web App's Log Stream we could see the following error repeated on each restart attempt …
Read MoreThis is another of those posts to remind me in the future. I searched the documentation for this answer for ages and found nothing, eventually getting the solution by asking on the SonarQube Forum
When you link SonarQube into an Azure DevOps pipeline that is used from branch protection the success, or failure, of the …
Read More- Whilst adding SonarQube analysis to a large project I started getting memory errors during the analysis phase. The solution was to up the memory available to the SonarQube Scanner on the my build agent, not the memory on the SonarQube server as I had first thought. This is done with an environment variable as per the …
Read More We have been looking migrating some of our common .NET Core libraries into new NuGet packages and have taken the chance to change our build process to use Azure DevOps Multi-stage Pipelines. Whilst doing this I hit a problem getting SonarQube analysis working, the documentation I found was a little confusing.
The …
Read MoreProblem
I recently tripped myself up whist adding SonarQube analysis to a rather complex Azure DevOps build.
The build has two VsTest steps, both were using the same folder for their test result files. When the first VsTest task ran it created the expected .TRX and .COVERAGE files and then published its results to …
Read More