We are using the SonarScanner for Azure DevOps and have just (automatically) updated to version 5.1.0.
Unfortunately, something seems to be broken with this version. When trying to run our pipeline with this version we are getting the following error even though nothing changed from our side:
Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1.2184:sonar (default-cli) on project xxx: Not authorized. Analyzing this project requires authentication. Please provide a user token in sonar.login or other credentials in sonar.login and sonar.password. -> [Help 1]
It was and still is working fine with version 5.0.0. We downgraded the version for now but would like to update as soon as this issue is fixed.
Anything we can do from our side or does anyone else have this issue as well?
A new version has been deployed just after this one and will fix that issue (you should see 1.23.1 as the prepare analysis configuration task version, might take some time to spread out).
Is 1.27.1 for SonarCloud supposed to fix the same issue for Azure DevOps with SonarCloud? It does not seem to resolve the issue for us at least:
Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1.2184:sonar (default-cli) on project xxxxxxxxxxx: You’re not authorized to run analysis. No sonar.login or SONAR_TOKEN env variable was set
Yes, just make sure that the Prepare Analysis configuration is show as 1.23.1, otherwise you’re still on the old one (not sure what happens, we also have some internal builds having the 1.27.1 of the extension itself installed, but still running the 1.23.0 version of the task (each of them + the extension have their own versionning), needed to change the vmImage to have it taken into account.