Massive performance issues in azure integration

[ganncamp (G Ann Campbell)]

Hi,

I’m sorry to hear the upgrade didn’t solve it. It’s odd to me that your first post-upgrade run of Project1 worked and the second run timed out.

I’m wondering if this could be relevant:

Analysis runs even though there is no Prepare task or any other sonarqube task in the pipeline

If: (a) you are using a self-hosted agent, and (b) a previous analysis pipeline failed without running the end/Run Code Analysis step, and (c) you then removed the analysis steps from the pipeline… … it’s possible that some of the clean-up that happens in the end/Run Code Analysis step won’t have completed. Some of our hooks into MSBuild could be still on disk, which would then impact future builds. If there are any .sonarqube folders under the build agent root folder, delete them then try …

Since your jobs keep timing out, I’m guessing that none of that end-step cleanup ever happens. Do you see .sonarqube directories on your build agent?

Also, could you take a look at this & see if it helps?

The Sonar guide for investigating the performance of .NET analysis

This guide is intended to help SonarQube and SonarCloud users investigate .NET analysis performance issues. This effort can lead to: self-diagnose and fix a performance issue gather information to open a well-defined topic on this community forum help SonarSource improve the performance of the products Before discussing how to investigate performance issues, you should first understand the different steps of the analysis. Introduction to the SonarSource .NET static analysis State-of-the-a…

And finally, I’m pretty close to being over my head here (glub, glub), so I’m going to flag this for more expert attention.

 
Ann