SonarQube Cloud Not Triggering New Scan on Commit Push to Existing Pull Request

SonarQube Cloud
1

Hi everyone,

We’re using SonarQube Cloud with automatic analysis and automatic binding of our GitHub organization and repositories. Here’s how the process currently works:

  • When a pull request is opened, SonarQube triggers an analysis, and everything works fine.
  • However, when a new commit is pushed to an existing pull request, SonarQube does not trigger a new scan.

Is this a limitation of the integration, or is there a configuration setting I can adjust to ensure that a new scan is triggered when a commit is pushed to a pull request? Alternatively, should I consider switching to a CI-based scan to handle this situation?

Any advice or insights would be greatly appreciated!

Details:

ALM used - GitHub
CI system used - github
Languages of the repository - GO

Thanks in advance!

2

Hi,

Welcome to the community!

I think this is the key (emphasis mine):

I.e. it looks like the trigger is the opening on the PR.

So yes, it’s probably time to switch to a self-managed CI-based analysis.

 
HTH,
Ann

3

Hi Ann,

Thanks for the response. We didn’t make any changes on our side, but the scans for new pushes to PRs are now working. It seems there was an issue with the integration between SonarCloud and GitHub.