How to diagnose and/or trigger a GitHub commit that never triggered SC?

SonarQube Cloud
1

Template for a good new topic, formatted with Markdown:

  • ALM used (GitHub)
  • CI system used (GitHub App)
  • Languages of the repository (Java)
  • Error observed (About once per week (1/100 PRs), a given push is not registered with SonarCloud, and the check, therefore is never reported back)
  • Steps to reproduce (Unable to reproduce, nor find useful log files)
  • Potential workaround (Pushing an empty commit sometimes works)

About 1% of our PRs receive no notification back from SonarCloud about the results of the test. There is no way to re-run or re-trigger the tests, so the only workaround that we’ve found is to push an empty commit, which is also not 100% reliable.

Is this a known problem?
Are there GitHub app logs that I can view to help track down where the breakdown happened?
Any other suggestions on how to retrigger a given commit in SonarCloud, to avoid having to re-run all test on a given commit?

1 Like
2

Hi,

To be clear, you’re initiating analysis “manually” (versus using automatic analysis) from your GitHub Actions pipeline?

 
Thx,
Ann

3

To be clear, you’re initiating analysis “manually” (versus using automatic analysis) from your GitHub Actions pipeline?

No. We have a SonarCloud installed as a GitHub App, which we can see here:
https://github.com/$org/$repo/settings/installations

The checks run automatically off of our private repos. Though I see mention of a GitHub action as an option, through this GitHub app, the checks fire automatically (except in the rare cases when they don’t).

4

Hi,

Okay, so you seem to be using automatic analysis. That only supports main branches.

 
Ann