SonarCloud not detecting/scanning PRs on private repos

SonarQube Cloud
, ,
1
  • ALM used: GitHub
  • CI system used: GitHub Actions
  • Scanner: SonarCloud Automated Analysis
  • Languages of the repository: TypeScript/JavaScript
  • Error observed: New PRs not displayed in SonarCloud Pull Requests, but a pending check is listed in GitHub for SonarCloud
  • Steps to reproduce: Random, open a PR
  • Workarounds: add an empty commit to the PR

Over the last week or so we have been seeing long delays or no attempts in SonarCloud to scan new pull requests. As this is a required step of our SDLC this is becoming a friction point for our developers.
Can you determine why we are seeing pull requests get ignored at random by SonarCloud?

1 Like
2

Hi,

Can you post or point to the analysis logs or the logs up to the point that analysis stalls / doesn’t happen?

 
Thx,
Ann

3

I can try to get some screenshots from GitHub to illustrate. There are no errors or logs, we’re just seeing new pull requests sometime take hours to appear in SonarCloud and/or receive scan results.
I have some teams migrating to GitHub Actions instead of the Automatic Analysis method in order to unblock their work.

4

Hi,

To be clear, are you seeing these delays with automatic analysis or on GH Actions?

 
Ann

5

We’re seeing the delays randomly when using Automatic Analysis.
Thanks for looking into this.

6

Hi,

Thanks for the details. Can you provide some dates/times when you saw slowness so that we can correlate to what was or was not going on on our end?

 
Thx,
Ann

8

I’m having the same issue on my private repositories. I noticed in my PRs list they stopped yesterday (well, I guess this morning - the last PR analysis was at 2:14 AM EST on July 12.) We have had 4 PRs since then, and none of them show up in the PR list. They also do not show up in pending list.

9

Hi All - we are currently investigating this issue. Yesterday we met with SonarCloud user Chris Johnson and he gave us some helpful repro steps. Today we hope to diagnose it and update you as soon as we can.

1 Like
11

We are seeing this behavior again in our private repos in Github. The last PR that was scanned was 18 hours ago. What was the root cause of the problem last time?

12

Hi,

Thanks for your report. It helped us find this:

https://community.sonarsource.com/t/automatic-analysis-slowdown-processing-github-prs/96466

You should see this start to get better soon, with full resolution by, let’s say mid-morning in Europe.

 
Thx,
Ann

13

https://community.sonarsource.com/t/automatic-analysis-slowdown-processing-github-prs/96466/2?u=colin

14

We have a similar problem where SonarCloud has not been detecting/scanning PRs on our private repo with automated analysis.

Just created two new PRs over 1 hour ago and they have not been scanned yet.

It appears that this issue is not fully resolved.

15

Hi @jb1,

Welcome to the community!

Thanks for joining the conversation. The SRE on duty just double-checked, and the backlog is cleared. So it seems your problem is unrelated.

Can you create a new thread and provide all your details, please?

 
Thx,
Ann