In my case, downgrade de version of docker image running for sonarqube-cli to: sonarsource/sonar-scanner-cli:10.0.3.1430_5.0.1
thank you, it work.
Does this mean we should refer to this file for the latest version wherever we automate the downloading of Sonarscanner CLI?
In the documentation, version 6.2.1 is marked as release though SonarScanner CLI
Yes, this file drives what is being shown in documentation.
That being said, be mindful of the fact that we can introduce breaking changes between scanner versions. If you’re always using the latest, you’ll be susceptible to your workflow breaking “by surprise”.
That’s clear, thank you.
One change I noticed from 5.x to 6.x is the added “-x64” suffix to the binaries files for example, in case someone else encountered 403 errors for this same reason.
A post was split to a new topic: 403 error downloading JRE
Hello,
I have the same error and I do not understand why…
@ct24p glad that you could resolve the issue. what was the problem ?
Edit :
Just needed to set sonar.host.url property in conf/sonar-scanner.properties to the URL of my hosted instance. Apparently, the default is now SonarCloud and before, this were http://localhost:9000