Must-share information (formatted with Markdown):
- SonarQube Developer Edition Version 10.1 (build 73491)
- how is SonarQube deployed: zip, Docker, Helm. Don’t know, I’m not the admin.
We use the SonarQubePrepare@4 task in Azure DevOps to set up scans of our source code. Recently (following an upgrade of SonarQube?), I’ve started to see this warning on the SQ home page:
The property ‘sonar.login’ is deprecated and will be removed in the future. Please use the ‘sonar.token’ property instead when passing a token.
However, AFAIK, I don’t set that property anywhere in my build pipelines or when creating a serviuce connection from my DevOps project to the SQ server. So, does the SonarQube extension for Azure DevOps need updating instead? (Analogous to what you seem to be doing for the Sonar Scanner for Jenkins here.)
It’s time to start using
SonarQubePrepare@5 (assuming you have v5.15 of the extension for Azure DevOps installed, and are not stuck on an old version)
Thanks; I didn’t know it had upgraded! (It would’ve been nice to have seen a simple warning from SQ like: “v4 of task XYZ is deprecated, consider upgrading it to v5 in your Azure DevOps pipeline”.)
Anyhow I’ve now upgraded all the SQ tasks - Prepare, Analyze and Publish - from v4 to v5 in my Azure DevOps pipelines. The good news is that the SQ UI is now showing me the scan results for branches other than just my main one again, and for PRs too. But the bad news is that the UI is still showing this warning:
The property ‘sonar.login’ is deprecated…
Any ideas please?
Scrub that! I now see that the “The last analysis has warnings” message in the SQ UI is specific to the branch you’re looking at. When I switch to the branch in which I had upgraded the SQ tasks the warning has disappeared; so hopefully it will disappear on the main branch as well once my branch has been merged in… (and it did disappear - case solved:).)
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.