Disable Github Pull Request enrichment

SonarQube Cloud
1

Dear SonarSource Team,

We are currently using the SonarCloud Team plan, which allows integration with a single binding. At present, our SonarCloud instance is integrated with Azure DevOps, enabling it to trigger analyses on pull requests and provide comments directly within them.

We are in the process of migrating our git repositories from Azure DevOps to GitHub. This transition has introduced some challenges. Since we cannot change the binding (as some repositories still reside in Azure DevOps while others have already moved to GitHub), we are experiencing failures in SonarCloud tasks within Azure DevOps pipelines that are triggered by GitHub pull requests.

These pipelines are initiated using GitHub pull request IDs, and SonarCloud attempts to interact with GitHub to comment on and enrich the pull requests. However, this fails because GitHub is not currently integrated with our SonarCloud setup.

We tried already multiple sulutions, like rewriting the branch or disabling sonar.pullrequest.github.summary_comment. Any suggestions?

2

Hey there.

What’s the specific failure you’re getting?

3

Caused by: com.sonarsource.scanner.engine.webapi.client.HttpException: Error 404 on https://sonarcloud.io/api/alm_integration/show_pullrequest?project=xxx&pullrequestKey=231 : {“errors”:[{“msg”:“Unable to find the pullrequest with key \u0027231\u0027”}]} at

So possible outcomes for me would be

  • We give sonarcube access to our github organization so it can decorate our github pullrequests. From what i can see this is not possible with the Team license to have multiple bound devops platforms. Is this true?
  • We disable functionality within sonarcube to decorate github pullrequests. We tried many settings, but with no luck.
4

Thank you @b0564914.

To clarify, the scanner first requests information from GitHub to facilitate the analysis process; PR decoration occurs later, after analysis results are submitted to SonarQube Cloud.

At this stage, it’s recommended to have two SonarQube Cloud organizations: one dedicated to your GitHub repositories (which will require new projects set up from scratch), and another for the existing repository connected to Azure DevOps.

Currently, projects cannot be unbound, so if you want to keep everything within a single organization and don’t need features related to PR decoration, your only option is to delete the existing project and create a manual project following the guidance in the SonarQube documentation. This would stop you from getting the error during scanning.