Question reg. ALM integration (GitHub)

SonarQube Server / Community Build
1
  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)

SonarQube Developer edition v9.8
(upgrade to v10 planned next week, but did not read anything related to this topic in release notes)

  • how is SonarQube deployed: zip, Docker, Helm

Docker

  • what are you trying to achieve

Configure ALM integration for GitHub so that commit checks are also published for branches (not only in Pull Requests)

  • what have you tried so far to achieve this

ALM integration is properly enabled, and feedback is available directly into Pull Request :+1:

Now we would like to also have SonarQube feedback published as commit check for commits in branch “master” (as example for the discussion).

Today, within a GitHub PR, 3 checks are published (2 from our Jenkins CI, 1 from SonarQube).
Once PR is merged into master, or if a change is directly pushed to master, only 2 checks are published (2 from Jenkins).

Is there a specific settings that we are missing, to tell SQ to publish commit checks also outside of a Pull Request analysis scope?

2

Hey there.

Have you made sure that the GitHub application has Read-only access on the Contents permission for this repo?

From the Upgrade Notes:

Release 9.0 upgrade notes

Reporting Quality Gate status on GitHub branches requires an additional permission
When working in private GitHub repositories, you need to grant read-only access to the Contents permission on the GitHub application that you’re using for SonarQube integration. See GitHub integration for more information.