We integrate with the SonarQube Server API to help our customers retrieve their data and transfer it to their destination.
However, we’ve observed that some customers are providing SonarQube Cloud subdomains instead of those intended for SonarQube Server. To prevent this, we would like to offer a predefined selection of valid subdomains used for SonarQube Server. Unfortunately, this information does not appear to be available in the API documentation. Could you please assist us with this?
If there are no fixed subdomains based on regions and they vary depending on customer-specific setups, how customers can reliably differentiate between a SonarQube Server subdomain and a SonarQube Cloud subdomain?
According to the customer, they are using SonarCloud and do not have a unique URL for a SonarQube Server. They are unsure what value should be entered in the subdomain field for our SonarQube Server connector.
They entered sonarcloud.io/organizations/anchorlabsinc as the subdomain, but the connector failed with the error message: “organization is missing”, since the organization parameter is required for the SonarCloud API.
Could you please clarify how they can determine the correct subdomain for SonarQube Server, or what steps they need to take to obtain the appropriate subdomain value in order to use the SonarQube Server connector?
I think we’re at an apples-and-oranges juncture. If you want to support SonarCloud users, you’ll need to accept the use of “sonarcloud.io” and add the ability to specify an organization key.