-
Bug
-
Resolution: Unresolved
-
Blocker
-
jenkins LTS 2.107.2
sonarqube scanner 2.7.1
After upgrade of sonarqube scanner plugin from 2.6.1 to 2.7.1, all jobs with sonar step configured have lost the link with 'Sonar server' configured in Jenkins > Manage > configure System > SonarQube servers.
Then, token used to contact API is no more loaded during job execution and step fails with 'Not authorized' error from Sonar. When checking each job configuration, there is indeed no more 'server' choice dropdown in configuration step.
This is a really annoying regression, as we have a lot of jobs that suffers from that. Workaround of adding credentials for each job is not really an option, as we have really a large impact.
Thanks for your help on that.