Sonarcloud not detecting new default branches or PRs on Github

SonarQube Cloud
,
1

We are using Sonarcloud with Github integration. Since the 17th of February we haven’t had any PR decorations.

The system is also no longer picking up our new default branches.

I checked the following:

  • Background tasks for anything that has failed, or is still pending. Found no activity.
  • Branches and PRs - it hasn’t picked up anything since the 17th.
  • the Github actions, keys and config files in the repo itself, everything is still there unchanged.

Not sure what else to check from here, is there anything that I can do further from my end to debug this?

2

I’m baffled as to why I’, paying a better part of £4k per month for a product that doesn’t have a proper support structure. I’ll resolve my issue by moving over to another SAST.

3

Hello,

Welcome to the community forum and sorry for the delay!

I see in your message that you are using Github Actions, do you have any error reported in the log of you actions ? Did it work before the 17th ?
Are you able to see the analyzed PR in SonarCloud and only the PR decoration is missing ? Or even the PR don’t appear on SonarCloud ?

Could you share privately with use your organization key and project key so that we can investigate further ?

4

Hi Gregoire,

Thanks for responding. Answers below:

1.) Do you have any error reported in the log of you actions?
Nothing shows up in the logs at all.

2.) Did it work before the 17th?
It worked perfectly up until the 15th.

3.) Are you able to see the analyzed PR in SonarCloud and only the PR decoration is missing ? Or even the PR don’t appear on SonarCloud ?
The PRs don’t even show up, and no new branches either.

I’ll send over the org keys now as a PM

5

I think we’re seeing a similar issue in SonarCloud. I presume the branch denoted as “MAIN” is supposed to be picked up from github via the integration, but that doesn’t seem to be happening. SonarCloud still thinks the main branch is an old feature branch that no longer exists in github. Also it seems that the regex for long-lived branches isn’t totally functioning properly because with my regex being “(develop|dev|qa|master|release).*”, the “dev” branch is marked as short-lived.

Any help Sonar team?