I am using SonarCloud with Azure DevOps to analyse 40+ Visual Studio (C#) projects, my ADO builds perform a number of tasks, including building the VS solutions in Debug configuration (with pdb symbols, etc.) followed by building the same solution in Release configuration for publishing.
I have noticed that enabling the SonarCloud Analysis can add a significant amount of time to the build, therefore in order to minimise the impact my SonarCloud analysis is enabled only for my debug build and I have achieved that until now by calling the ‘Publish Quality Gate Result’ before my Release build, you can see here the Build - Release step takes only a few seconds (and the build logs for this step shows no sonar cloud activity):
Since Monday however I have seen that SonarCloud is also scanning my Release build even if it is happening after the ‘Publish Quality Gate Result’ step and as you can see below this is adding a not insignificant delay to my builds:
So the question is, if something has changed in the behaviour of the SonarCloud tasks for Azure DevOps, how do I get these tasks to behave as they were doing before this change?