How to separate SonarCloud Organizations for Different Teams or Projects

SonarQube Cloud
1

Summary

I’d like to clarify the relationship between GitHub organizations and SonarCloud.
Specifically, I’m interested in whether it’s possible to create multiple SonarCloud organizations linked to a single GitHub organization.

Background

We’re currently using a SonarCloud organization that corresponds directly to our GitHub organization.
But, there has been a need to delineate SonarCloud organizations on a departmental basis for our single github organization.

Question

Can we create separated SonarCloud organizations for different teams or projects while still operating under repositories on our single GitHub organization?
Or do we need to create a new GitHub organization and move the repositories to the new GitHub organization accordingly?

  • ALM: GitHub
  • CI: GitHub Actions
  • Scanner: SonarScanner For GitHub Actions
  • Languages: Go, Typescript
  • SonarCloud project is private
2

Today, it is not possible. One GitHub org can be linked to one SonarCloud organization.

I would hate for SonarCloud to be the driver for that decision, but yes, in order to have more than 1 SonarCloud org, you’ll need more than 1 GitHub org.

Hopefully in 2024 as we work towards some big objectives on SonarCloud and getting it ready for larger teams, we might see some improvements in this area.

3

Thank you for your replay.

Hopefully in 2024 as we work towards some big objectives on SonarCloud and getting it ready for larger teams, we might see some improvements in this area.

Could you let me know what features SonarCloud team to improve about organization in 2024?
If you can, I want to know whether this issue’s feature will be implemented.
And, if this issue’s feature will be implemented, when will this issue’s feature be implemented?

4

I don’t have specific details to share at this point in time.