Hi Simon,
Out of interest how long are your Sonarcloud runs taking to complete?
If its anything to go off we have a .netFrameworks which takes forever to run normally. Some pipelines run for 30 minutes others around 1 hour.
We have about 13 .csproj files in a Solution. To run every single one in one agent normally takes 35 minutes but with Sonar analysis it goes on over 6 hours which makes it unfeasible. Thats a single sonar project per cs proj rather than solution (it breaks down projects which gives us areas to focus on).
To make the Sonar Analysis work we had to make it so that we do one Sonar Analysis per build agent. We have a build agent that runs that detects folder changes then only specific agents run depending on what changed. In this PR it shows only two of our projects changed so only two sonar build agents ran.
The picture below (heavily redacted) shows two projects running. Some take up to an hour to run. The devs submit their PR, it runs in the background and they do other things.
We can make it faster with selfhosted build agents (Azure VMs with more power). We are migrating to.netcore and for the projects running on this, its ran a lot faster.