Warning; SonarQubePrepare@6, SonarQubePublish@6, SonarQubeAnalyze@6 are deprecated

SonarQube Server / Community Build
1

  • which versions are you using SonarQube 10.6.0.92116

  • Issue
    We are seeing heaps of SoanrQube ADO task deprecating warning messages in across all of our ADO pipelines running in our ADO org.

  • ##[warning]Task 'Prepare Analysis Configuration' version 6 (SonarQubePrepare @ 6) is deprecated. *##[warning]This task is deprecated. Please upgrade to the latest version. For more information, refer to https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/scanners/sonarqube-extension-for-azure-devops/

  • ##[warning]Task 'Run Code Analysis' version 6 (SonarQubeAnalyze @ 6) is deprecated.

  • ##[warning]Task 'Publish Quality Gate Result' version 6 (SonarQubePublish @ 6) is deprecated.

However, it seems like v7 tasks are only mentioned on SonarQube doco (release 2024-10-21): SonarQube extension for Azure DevOps (Version @ 6 tasks were deprecated in v7.0 and will be dropped in a subsequent release. )

And there’s no v7 info on ADO documentation yet - only v6 tasks are available: SonarQubePrepare @ 6 - Prepare Analysis Configuration v6 task | Microsoft Learn

Can you please advise the release date of @ 7 tasks and why we are seeing the deprecation warnings while @ 7 tasks are not actually available?

Thanks!

2

Hi @elliechen-seau

This deprecation and warning is standard procedure when we release a new version of a task. This does not mean the task will stop working right away.

As for the documentation, this is maintained by Microsoft. We will get in contact with them to see how to speed up the process. Rest assured the v7 tasks are indeed available since you have the updated version of the extension.

Denis

1 Like
3

Hi Denis,
Thanks for the prompt reply!
Please reach out to Microsoft and would be great if you can come back and provide us an ETA on when Microsoft is ready to update their documentation. We would be hesitated to perform the upgrade without having the official documentation as a reference point. Saying that, it’s good to know that this is not a glitch but just serves as a warning and we shouldn’t be too concerned about it.
Thanks again!