Azure DevOps Publish Quality Gate Hanging

Get help SonarCloud
#1

Running a scan in Azure DevOps of a C# project, the analysis step completes successfully, but the step publishing the quality gate is hanging. It worked successfully on 2020-09-11T16:06:29.5983654Z but stopped working sometime before 2020-09-11T18:05:00.6613798Z. We have a timeout set on this job/pipeline, and it’s hitting that. Here’s the output from the task:

Starting: Publish Quality Gate Result
==============================================================================
Task         : Publish Quality Gate Result
Description  : Publish SonarCloud's Quality Gate result on the Azure Pipelines build result. To be used after the actual analysis.
Version      : 1.9.0
Author       : sonarsource
Help         : [More Information](http://redirect.sonarsource.com/doc/install-configure-scanner-tfs-ts.html)
==============================================================================
##[error]The operation was canceled.
Finishing: Publish Quality Gate Result
4 Likes
#2

Getting the same issue here.

2 Likes
#3

Same here as well.

#4

Issue : Quality Gate failed: Compute engine task did not complete within time please comment it here as well so it will be addressed asap

#5

We have this issue as well.

#6

Also happening for us.

Issue : Quality Gate failed: Compute engine task did not complete within time
#7

problem with the sonar quality gate
Issue : Quality Gate failed: Compute engine task did not complete within time I have put the details out here and waiting for @sonarsourcers to respond/acknowledge and no response yet, almost 3 hours now!

1 Like
#8

This is still occurring. @sonarsourcers - anyone looking into this? can this at least be acknowledged ?

#9

There is a SonarSource outage, please consolidate in this thread:

#10

It broken for us around noon central yesterday (9/11).

#11

Hi there,

There was an outage on our side starting friday evening, the queue has been processed in the following night, everything should be back to normal now, if not, please tell us again.

Thank you for your understanding and sorry for the inconvenience.

Mickaël

#13