Hi Simon,
We have the sonar host url configured through the plugin on the Jenkins master configuration:
To run the analysis we use the official sonarsource/sonarcloud-scan docker image (so it is always the one tagged latest, with an always pull policy) and call a shell script step directly on it. Snippet from our Jenkinsfile:
container('sonar-scanner') {
withSonarQubeEnv('SonarCloud') {
sh 'sonar-scanner.sh'
}
}
Our sonar-project.properties contains sonar.projectKey and sonar.organization but not sonar.host.url. The shell script does not set sonar.host.url either. We let the Sonar Plugin take care of that which is what the withSonarQubeEnv('SonarCloud')
is for in our Jenkinsfile.
The project has been created a few months ago and we have not deleted it since. I’ll send you that information privately.
For the versions:
- Jenkins 2.190.1
- Blue Ocean 1.19.0
- SonarQube Scanner for Jenkins 2.9