.NET project with Azure Pipelines

Using YAML or the Azure Classic editor to create the Azure build pipeline for .Net projects.

The setup is different depending on whether you use YAML or the Azure Classic interface.

The use of the Classic editor is not always possible (e.g. if your code is stored on GitHub).
If you use YAML, SonarSource can provide you with YAML templates or code examples.

Before you start

Before you begin, read About Azure Pipelines integration.

The prerequisites are:

The Azure DevOps Extension is installed in your Azure DevOps organization: see Azure DevOps Extension.
Your project is created in SonarQube Server (see Importing your Azure DevOps repository) and configured for Azure Pipelines (see Setting up Azure integration for your project).
The pull request and branch analysis are enabled in your pipeline.

If you need to use a specific scanner version, see Using Azure DevOps extension's features.

Analysis parameters can be set at different levels, see Importing your Azure DevOps repository. When creating your pipeline, you will have to enter the project key and you may also enter the project version and name. For more information about these task inputs, see Task inputs specific to the .NET mode. You may define additional parameters in this task. In that case, these parameters have precedence over parameters defined at the project or global level.

Using YAML

Add the following SonarQube tasks to your YAML pipeline:

Before your build task, add a Prepare Analysis Configuration task.
After your build task, add a Run Code Analysis task.
After the Run Code Analysis task, add a Publish Quality Gate Result task.

See the YAML file example below. Also, see the YAML pipeline templates. For information about the SonarQube task inputs, see SonarQube tasks for Azure Pipelines.

Make sure the SonarQube task version used in your YAML file is the correct one. For example, in SonarQubePrepare@7, 7 should correspond to the version of the Azure DevOps Extension you’re using.

YAML file example

trigger:
- main # or another name representing your main branch
- feature/*

steps:
 # Checkout the repository 
- checkout: self

 # Disable shallow fetch
  fetchDepth: 0

# Prepare Analysis Configuration task
- task: SonarQubePrepare@8
  inputs:
    SonarQube: '<YourSonarqubeServerEndpoint>'
    scannerMode: 'dotnet'
    projectKey: '<YourProjectKey>'

# Dotnet build task
- task: DotNetCoreCLI@2
  displayName: 'dotnet build'

# Run Code Analysis task
- task: SonarQubeAnalyze@8

# Publish Quality Gate Result task
- task: SonarQubePublish@8
  inputs:
    pollingTimeoutSec: '300'

Using the Classic editor

To add the analysis to your classic build pipeline:

In the Azure DevOps Classic editor, create or update your build pipeline.
Add a Prepare Analysis Configuration task before your build task:
- In SonarQube Server Service Endpoint, select the SonarQube service connection you created during setup. See the Setting up Azure integration for your project page for more information about adding a connection.
- Under Choose a way to run the analysis, select Integrate with MSBuild.
- In the Project key field, enter your project key.
- Optionally, enter the project name and version.
Add a new Run Code Analysis task after your build task.
Add a new Publish quality gate Result on your build pipeline summary.
Ensure that the pipeline runs automatically for all the branches you want:
- Under the Triggers tab of your pipeline, select Enable continuous integration and select all the branches for which you want SonarQube Server analysis to run automatically.
Save your pipeline.

Configuring your scanner

If you're using the .NET scanner to complete the analysis, see the Configuring the scanner for NET page for language-specific details.

There's also an article about running Multi-language analysis for select languages when the sonar.scanner.scanAll parameter is enabled via the extraProperties listed in your Prepare Analysis Configuration task.

There's also an article about running Prepare Analysis Configuration task.

For a full explanation of how to pass properties to the SonarScanner for .NET, including when to use the /d: prefix versus bare properties in extraProperties, see Passing properties to the SonarScanner.