Private project not getting checks posted on GitHub

SonarQube Cloud
1

We have private projects hosted on SonarCloud and GitHub. As part of our PR checks we require the Sonar Check to be passing before merging to ensure best quality.

We have a PR on a smaller repo that is not getting the Sonar Check registered with GitHub. It worked fine for an other PR last week and it seems to work fine for PR on all our other projects.

We tried:

  • re-running the pipeline to force a re-run of sonar-scanner.
  • delete the PR from SonarCloud and re-run.

We ended up with a duplicated Sonar report posted in the PR comments, but no checks got posted, blocking the PR. We have not changed any config from our side and we suspect that the API call to send the checks notification to GH is failing. We have seen similar behavior in the past but that has been working well in the past couple of years.

Since this is a private project I cannot share much more details publicly.

image
image1892×2088 330 KB

2

Here is a screenshot for a Merged PR on the same project where the check reported without any issue:

image
image1710×276 34.2 KB

3

@ganncamp We are still experiencing this with the same project but it works fine for other ones. We do suspect that the bulk of the problem is on the GitHub side since we see it happen with non sonar checks, but it would be good to get more visibility into the notifications being sent from SonarCloud to the GitHub APIs so we can then file bug reports with GitHub support.

4

Hi,

Can you provide org and project IDs, as well as an approximate date/timestamp for this?

 
Thx,
Ann

6

I provided details privately since this is a private repo. We did contact GitHub support and they told us to reach to SonarSource support.

8

Hi,

Thanks for those details. I’ve flagged this for people with better log access than I have. :smiley:

 
Ann

9

I’m getting reports of the same issue with other private projects in our org. Luckily our primary projects are not impacted as much, yet, but this seems to be getting worse somehow.

13

Hello @sodul,

Somehow this one slipped our minds… sorry for the delay. Do you still have the problem on your repo? If yes, could you please trigger an analysis with PR decoration so I have a recent occurence to look for in our logs?

Thanks

Antoine

1 Like
14

That project is no longer getting activity so it is no longer an ‘active issue’ for us.

15

Thanks for confirming @sodul.

We wont further investigate then. Please create a new thread if this happens again.

Cheers,
Antoine