Environment:
-
SonarQube Edition: Community Build v26.3.0.120487 (self-hosted, Docker)
-
CI/CD: Azure DevOps — Azure Pipelines
-
SCM: GitHub — multiple separate GitHub accounts/organizations
Current Setup:
We run a single SonarQube Community instance deployed via Docker. One project (ABC Web App) from GitHub Account A is currently configured and scanning successfully through Azure Pipelines. The pipeline sends results to SonarQube using SONAR_HOST_URL and a project-scoped SONAR_TOKEN.
What I Want to Achieve:
Onboard a second project (ABC Mobile App) from a different GitHub account/org (GitHub Account B) onto the same SonarQube Docker instance — without spinning up a separate SonarQube instance.
My Questions:
Q1 — Basic multi-project scanning (Community Edition): Is it supported to scan projects from two different GitHub accounts/organizations on the same Community instance? My understanding is that SonarQube projects are independent entities identified by sonar.projectKey, so the GitHub account origin shouldn’t matter at the scanner level. Is this correct? Can I simply:
-
Create a new project in SonarQube UI for
ABC-mobile-app -
Generate a new project token
-
Configure a new Azure Pipeline pointing to the same
SONAR_HOST_URLwith the newsonar.projectKey
…and have both projects scan independently?
Q2 — Does Developer Edition resolve this?
What I Haven’t Tried Yet:
I haven’t configured the second project yet, as I want to confirm the supported approach before making changes