Introduction

Adding SonarQube Server analysis to your Azure pipeline.

Before you begin, see Azure Pipelines integration overview.

Once you have created and set up your SonarQube Server project, see Creating and configuring your Azure DevOps project and Setting up Azure integration for your project, you can add the SonarQube Server analysis to your Azure build pipeline:

• Gradle or Maven project

• .NET project

• C family project

• JS, TS, Go, Python, PHP, etc. project

• Monorepo projects

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.

Once you have added the SonarQube Server analysis to your build pipeline, you can check the SonarQube Server Quality gate status in release pipeline.

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.

Related pages

• Azure Pipelines integration overview

• Setting up Azure DevOps integration at global level

• Creating and configuring your Azure DevOps project

• Setting up Azure integration for your project at the project level

• Troubleshooting analysis