Adding analysis to your Azure pipeline

General guidelines to add SonarQube Server analysis to your Azure pipeline.

The Azure DevOps Extension for SonarQube Server must be installed in your Azure DevOps organization: see Azure DevOps Extension.

1. Before you begin, see About Azure Pipelines integration.
2. Create your SonarQube Server project, see Importing your Azure DevOps repository.
3. Set up your project integration with Azure Pipelines. See Setting up Azure integration for your project.
4. Add the SonarQube Server analysis to your Azure build pipeline:

   • Gradle or Maven project with Azure Pipelines

   • .NET project with Azure Pipelines

   • C family project with Azure Pipelines

   • JS, TS, Go, Python, PHP, etc. project with Azure Pipelines

   • Monorepo projects with Azure Pipelines

5. Once you have added the SonarQube Server analysis to your build pipeline, you can check the SonarQube Server Quality gate status in release pipeline.
6. If you want to decorate your pull request with a quality gate status and are not interested to have SonarQube Server annotations in your PR, see the Disable pull request annotations article.

The Azure DevOps extension for SonarQube Server running in your Azure pipeline can automatically detect branches or pull requests being built. You don’t need to specifically pass them as parameters to the scanner but you should make sure you have set up the pull request integration in your project. See Setting up Azure integration for your project for more information.

Related pages

• About Azure Pipelines integration

• Binding to Azure DevOps

• Importing your Azure DevOps repository

• Setting up Azure integration for your project

• Troubleshooting analysis with Azure

Related online learning

• Configuring code analysis for SonarQube Server with Azure Pipelines
• Configuring pull request decoration for SonarQube Server using Azure DevOps