Azure DevOps Extension
The Azure DevOps Extension for SonarQube Server makes it easy to integrate analysis into your build pipeline, allowing you to analyze all supported languages.
The Azure DevOps extension for SonarQube Server makes it easy to integrate analysis into your Azure build pipeline. The extension allows the analysis of all languages supported by SonarQube Server. For more information, see Azure Pipelines integration overview.
This page explains how to install the extension. Once the integration at a global level with Azure DevOps is complete, and you have set up project integration, you can Add SonarQube analysis to your pipeline.
Installation requirements
Category
Requirement
Azure DevOps
The extension will work with these Azure product versions:
• Azure DevOps Services
• Azure DevOps Server 2022.2
• Azure DevOps Server 2020.1.2
• Azure DevOps Server 2019.1.2
Azure pipeline agents
The extension will work with all of the hosted agents (Windows, Linux, and macOS):
• If you are using Microsoft-hosted agents, there is nothing else to install.
• If you are self-hosting the agents, see General requirements on scanner environment. In addition, make sure the appropriate build tools are installed on the agent for the type of project you are analyzing. For example, .NET Framework v4.6.2+/NET Core 3.1+ if building using MSBuild, Maven for Java projects, etc.
The minimum agent version for @8 tasks of the Azure DevOps Extension for SonarQube Server is 3.218.0.
Allowed websites
In order to download binaries and communicate with SonarQube Server, the following URLs should be whitelisted:
• SonarQube base URL.
• If using the Maven/Gradle mode or not using the default version of SonarScanner for .NET or CLI: the Sonar binaries site (binaries.sonarsource.com).
If your instance of SonarQube Server is secured
If your SonarQube Server instance is secured behind a proxy and a self-signed certificate, you must add the self-signed certificate to the trusted CA certificates of the SonarScanner. In addition, if mutual TLS is used, you must define the access to the client certificate at the SonarScanner level.
See TLS certificates on client side and Securing behind a proxy.
Installing the extension
Sign in to your Azure DevOps Services organization or Azure DevOps Server collection with the dedicated technical account you created in Setting up Azure DevOps integration at global level.
From the Visual Studio Marketplace, install the Azure DevOps extension for SonarQube by selecting the Get it free button.
If upgrading from a previous version of the extension
Smooth migration
The latest version of the Azure DevOps extension for SonarQube embeds the latest version of SonarScanner for .NET and SonarScanner CLI. However, to allow a smooth migration, you can set up your Azure build pipeline to use a previous version of one of these scanners and thus, continue using a previous SonarQube tasks version until you’re ready to upgrade. See Using various features.
Prepare analysis configuration task: new scanner mode values
Allowable values for the scannerMode required property of the SonarQube tasks (see SonarQube tasks for Azure Pipelines) have changed with the v7 extension. Please use the following in your @8 tasks:
dotnetfor the .NET modeclifor the CLI modeotherfor the Maven / Gradle mode
Deprecation notices
@7 tasks are deprecated in v8.0 of the extension and will be dropped in a subsequent release.
@5 and @6 tasks were dropped in v8.0 of the extension.
Previous versions
As new scanner versions are released, previous requirements and/or planned deprecations will be listed here.
Related pages
Last updated
Was this helpful?