SonarQubeAnalyze@5 task deprecations Documentation clarification for Azure DevOps Services

SonarQube Server / Community Build
, ,
1

We are using SonarQubeAnalyze@5 on Azure DevOps Services and we started to recieve message below:

##[warning]This task is deprecated. Please upgrade to the latest version. For more information, refer to SonarQube extension for Azure DevOps

SonarScanner for MSBuild 5.15.1

  • how is SonarQube deployed: zip

Documentation specifies that it is not suportted for Azure DevOps services. Can you please provide update on documentation?
Please let us know if we would be out of support with next version and what it is timeline for it?

image
image842×823 64.3 KB

4

Thanks for raising this question, @Kosta.

Tasks 5.x and 6.x are both compatible with Azure DevOps Services.

  • I’ll add Azure DevOps Services to the 6.x compatibility list; it will be published in a few hours.

This raised the point that no clear deprecation policy exists for our scanners and integrations. I funneled the information to the appropriate team.

  • Meanwhile, note that version @6 task code also works with the SonarQube 9.9 LTA.
  • And if you need to stay on version @5, it’s possible to specify the exact .NET or CLI scanner version by using the msBuildVersion and cliVersion properties.
1 Like
6

What would happen if we use @5 task as it is, without msBuildVersion and cliVersion properties.?

For example we use this for MsBuild task

  • task: SonarQubePrepare@5
    displayName: ‘Configure SonarQube Prepare’
    enabled: true
    inputs:
    SonarQube: ‘ServiceConnectionName’
    projectKey: ‘KeyApp’
    projectName: ‘KeyApp’
    extraProperties: |
    # Additional properties that will be passed to the scanner,
    # Put one key=value per line, example:
    sonar.cs.vstest.reportsPaths=$(Agent.BuildDirectory)\testresults
    sonar.cs.vstest.reportsPaths=$(Agent.BuildDirectory)\testresults*.trx
    sonar.dependencyCheck.reportPath=$(Agent.BuildDirectory)\TestResults\dependency-check-report.xml
    sonar.dependencyCheck.htmlReportPath=$(Agent.BuildDirectory)\TestResults\dependency-check-report.html
7

@Kosta

If you use the v5 task right now, it will use the v5 scanner, no matter what.

If you use the v6 task, you have the option to specify msBuildVersion or cliVersion.

I hope that helps.