Hi, I’m with a consultancy where we use GitHub & SonarCloud internally. No complaints!
We’ve recently recommended SonarCloud to a client who also uses GitHub. We’re now faced with a bit of a predicament as it appears a single GitHub account can’t be paired with multiple SonarCloud Organisations.
Given licensing on the GitHub side of things coupled with the hassle of multiple accounts, I’m looking to see if anyone has any suggested workarounds here?
Thanks in advance…
Welcome to the community!
I confirm this is the case. To be precise, we recommend pairing (binding) your SonarCloud organization to a GitHub organization (not a user GitHub account), and this is a 1-to-1 relationship.
I don’t see why you would want to bind the same SonarCloud organization to multiple GitHub organizations. Can you please clarify your use case?
We’ve got a mix of public repos in our github organisation, and some private repos.
Our public repos are tied to an existing sonarQube account, but we want to use a different sonarqube project for our private repos.
Is that an architectural failing - should we be using the same Sonar organisation for both the public and private repos ?
Hello @andylockran ,
Welcome to the community!
Yes, there should be a one-to-one binding between your GitHub organization and the SonarCloud one. You can have a mix of public and private projects within one SonarCloud organization as well.