Sonarcloud Code Analysis Status in PR is Pending

First of all this has been seen quite a few times last year.

We have configured Sonarcloud for Automatic analysis. But we are unable to merge the PRs since the sonarcloud status is not getting success. But in the sonarcloud UI it’s shown as success. Will have to wait 15 to 30mins. We currently have a Paid plan.
Attaching the screenshots

Hey @alexypuli

First thing to check – has the PR been analyzed by SonarQube Cloud? Do you see it under Pull Requests in your project, and if so is there an analysis failure indicated when loading the PR?

Do you mean the status always eventually shows up and is just delayed, or does it never show up at all?

The PR been analysed by SonarQube Cloud. It’s under Pull Requests in your project and its status is successful.
The status always eventually shows up and is just delayed. Typically taking 15mins or more.

Thank you for your patience, @alexypuli, and apologies for the delayed response—I’ve been traveling. There are a few key factors we should consider when investigating the delays:

  • The initiation of Automatic Analysis might be experiencing delays, contributing to the overall wait time.
  • The duration of the Automatic Analysis itself could be longer than usual, which impacts report processing and the timing of PR decoration.
  • Report processing may be queued if other analyses are running simultaneously for the same project, causing further delays.
  • There can also be a delay between the completion of report processing and the actual start of PR decoration.

To identify where the bottleneck is occurring, would you be able to time each step?

  • After you open a PR in GitHub, does a PR analysis appear as ‘in progress’ (in the Pull Requests tab of your project) right away?
  • How long after opening the PR does the background task to process the analysis report start?
  • Once report processing finishes, does PR decoration appear immediately, or is there a notable delay?

Gathering this timing information will help us pinpoint where the slowdown occurs and identify potential solutions (or at least which team I should engage)!

Hi,

I missed this one. It seems issue doesn’t persist.