SonarCloud can't find server only on pull requests

It looks like SonarCloud is using the wrong server address on pull requests:
SonarQube server [http://localhost:9000] can not be reached
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin: (default-cli) on project tablesaw-parent: Unable to execute SonarQube: Fail to get bootstrap index from server: Failed to connect to localhost/ Connection refused (Connection refused) -> [Help 1]

However, I have no issues on the master branch

I’m using GitHub, Travis, and Java

Hi @benmccann,
Can you share here in what way(s) you specify the SonarCloud URL currently?

You may also want to check this page (although it is for SonarQube, this may help I think).

I don’t specify the SonarCloud URL anywhere. It seems to work correctly like that on the master branch and I’d expect the default to point to the SonarCloud servers. Is it required to specify it?

The scanner alone doesn’t know the URL of SonarCloud. Ideally it should come from some helper tool (such as the Travis add-on), or else specified through other means (the environment variable SONARQUBE_SCANNER_PARAMS or the Java property).

Are you using the Travis add-on? How do you configure the execution of the mvn command?

Yes, I’m using the Travis add-on. See here for the configuration:

@janos @AlxO thanks for looking at this. Any ideas why SonarCloud might not be working on GitHub pull requests for me based on the information provided?