Azure DevOps integration

1. In Azure DevOps, create or edit a Build Pipeline, and add a new Prepare Analysis Configuration task before your build task:
   • Select the SonarQube server endpoint you created in the Adding a new SonarQube Service Endpoint section.
   • Under Choose a way to run the analysis, select Integrate with Maven or Gradle.
   • Expand the Advanced section and replace the Additional Properties with the following snippet:
     • # Additional properties that will be passed to the scanner,
# Put one key=value per line, example:
# sonar.exclusions=**/*.bin
sonar.projectKey=YourProjectKey
2. Edit or add a new Maven or Gradle task
   • Under Code Analysis, check Run SonarQube or SonarCloud Analysis.
3. Add a new Publish quality gate Result on your build pipeline summary.
4. Under the Triggers tab of your pipeline, select Enable continuous integration, and choose all of the branches for which you want SonarQube analysis to run automatically.
5. Save your pipeline.

.yml example:

trigger:
- master
- feature/*

steps:
# Prepare Analysis Configuration task
- task: SonarQubePrepare@4
  inputs:
    SonarQube: 'YourSonarqubeServerEndpoint'
    scannerMode: 'Other'
    extraProperties: 'sonar.projectKey=YourProjectKey'

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

1. In Azure DevOps, create or edit a Build Pipeline, and add a new Prepare Analysis Configuration task before your build task:
   • Select the SonarQube server endpoint you created in the Adding a new SonarQube Service Endpoint section.
   • Under Choose a way to run the analysis, select Integrate with MSBuild.
   • In the project key field, enter your project key.
2. Add a new Run Code Analysis task after your build task.
3. Add a new Publish quality gate Result on your build pipeline summary.
4. Under the Triggers tab of your pipeline, select Enable continuous integration, and choose all of the branches for which you want SonarQube analysis to run automatically.
5. Save your pipeline.

.yml example:

trigger:
- master
- feature/*

steps:
# Prepare Analysis Configuration task
- task: SonarQubePrepare@4
  inputs:
    SonarQube: 'YourSonarqubeServerEndpoint'
    scannerMode: 'MSBuild'
    projectKey: 'YourProjectKey'

# Run Code Analysis task
- task: SonarQubeAnalyze@4

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

1. In Azure DevOps, create or edit a Build Pipeline, and add a new Prepare Analysis Configuration task before your build task:
   • Select the SonarQube server endpoint you created in the Adding a new SonarQube Service Endpoint section.
   • Under Choose a way to run the analysis, select Use standalone scanner.
   • Select the Manually provide configuration mode.
   • In the Project Key field, enter your project key.
2. Add a new Run Code Analysis task after your build task.
3. Add a new Publish quality gate Result on your build pipeline summary.
4. Under the Triggers tab of your pipeline, select Enable continuous integration, and choose all of the branches for which you want SonarQube analysis to run automatically.
5. Save your pipeline.

.yml example:

trigger:
- master
- feature/*

steps:
# Prepare Analysis Configuration task
- task: SonarQubePrepare@4
  inputs:
    SonarQube: 'YourSonarqubeServerEndpoint'
    scannerMode: 'CLI'
    configMode: 'manual'
    cliProjectKey: 'YourProjectKey'

# Run Code Analysis task
- task: SonarQubeAnalyze@4

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

In your build pipeline, insert the following steps in the order they appear here. These steps can be interweaved with other steps of your build as long as the following order is followed. All steps have to be executed on the same agent.

1. Make the Build Wrapper available on the build agent: Download and unzip the Build Wrapper on the build agent (see the Prerequisites section of the C/C++/Objective-C page). The archive to download and decompress depends on the platform of the host. Please, note that:
   • For the Microsoft-hosted build agent, you will need to make the Build Wrapper available on the build agent every time (as part of the build pipeline). To accomplish this, you can add a PowerShell script task by inserting a Command Line task. Example of PowerShell commands on a Windows host:
     Invoke-WebRequest -Uri '<sonarqube_url>/static/cpp/build-wrapper-win-x86.zip' -OutFile 'build-wrapper.zip'
Expand-Archive -Path 'build-wrapper.zip' -DestinationPath '.'
Example of bash commands on a Linux host:
     curl '<sonarqube_url>/static/cpp/build-wrapper-linux-x86.zip' --output build-wrapper.zip
unzip build-wrapper.zip
Example of bash commands on a macos host: curl '<sonarqube_url>/static/cpp/build-wrapper-macosx-x86.zip' --output build-wrapper.zip
unzip build-wrapper.zip
   • For the self-hosted build agent you can either download it every time (using the same scripts) or only once (as part of manual setup of build agent).
2. Add a Prepare analysis Configuration task and configure it as follow: Click on the Prepare analysis on SonarQube task to configure it:
   • Select the SonarQube Server.
   • In Choose the way to run the analysis, select standalone scanner (even if you build with Visual Studio/MSBuild).
   • In Additional Properties in the Advanced section, add the property sonar.cfamily.build-wrapper-output with, as its value, the output directory to which the Build Wrapper should write its results: sonar.cfamily.build-wrapper-output=<output directory>
3. Add a command line task to run your build. For the analysis to happen, your build has to be run through a command line so that it can be wrapped-up by the build-wrapper. To do so,
   • Run Build Wrapper executable. Pass in as the arguments: 
     1. The output directory configured in the previous task and 
     2. The command that runs a clean build of your project (not an incremental build). Example of PowerShell commands on a Windows host with an MSBuild build:
        build-wrapper-win-x86/build-wrapper-win-x86-64.exe --out-dir <output directory> MSBuild.exe /t:Rebuild
Example of bash commands on a Linux host with a make build:
        build-wrapper-linux-x86/build-wrapper-linux-x86-64 --out-dir <output directory> make clean all
Example of bash commands on a macos host with a xcodebuild build:
        build-wrapper-macosx-x86/build-wrapper-macos-x86 --out-dir <output directory> xcodebuild -project myproject.xcodeproj -configuration Release clean build

4. Add a Run code analysis task to run the code analysis and make the results available to SonarQube. Consider running this task right after the previous one as the build environment should not be significantly altered before running the analysis.
5. Add a Publish quality gate result task.

.yml example:

trigger:
- master
- feature/*

steps:
# Make Build Wrapper available
- task: Bash@3
  displayName: Download Build Wrapper
  inputs:
    targetType: inline
    script: >
      curl  '<SONARQUBE_HOST>/static/cpp/build-wrapper-linux-x86.zip' --output build-wrapper.zip
      unzip build-wrapper.zip

# Prepare Analysis Configuration task
- task: SonarQubePrepare@4
  inputs:
    SonarQube: 'YourSonarqubeServerEndpoint'
    scannerMode: 'CLI'
    configMode: 'manual'
    cliProjectKey: 'YourProjectKey'
    extraProperties: "sonar.cfamily.build-wrapper-output=bw_output"
# Command Line task to run your build.
- task: Bash@3
   displayName: Bash Script
   inputs:
     targetType: inline
     script: |
       ./build-wrapper-linux-x86/build-wrapper-linux-x86-64 --out-dir bw_output <Your build command>

# Run Code Analysis task
- task: SonarQubeAnalyze@4

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

Pull request decoration for a mono repository setup is supported starting in Enterprise Edition.

In a mono repository setup, multiple SonarQube projects, each corresponding to a separate project within the mono repository, are all bound to the same Azure DevOps repository. You'll need to set up pull request decoration for each SonarQube project that is part of a mono repository.

To add pull request decoration to a project that's part of a mono repository, set your project up manually as shown in the Adding pull request decoration to a manually created or existing project section above. You also need to set the Enable mono repository support setting to true at Project Settings > General Settings > Pull Request Decoration.

After setting your project settings, you need to ensure the correct project is being analyzed by adjusting the analysis scope and pass your project names to the scanner. See the following sections for more information.

Ensuring the correct project is analyzed

You need to adjust the analysis scope to make sure SonarQube doesn't analyze code from other projects in your mono repository. To do this set up a Source File Inclusion for your project at Project Settings > Analysis Scope with a pattern that will only include files from the appropriate folder. For example, adding ./MyFolderName/**/* to your inclusions would only include analysis of code in the MyFolderName folder. See Narrowing the Focus for more information on setting your analysis scope.

Passing project names to the scanner

Because of the nature of a mono repository, SonarQube scanners might read all project names of your mono repository as identical. To avoid having multiple projects with the same name, you need to pass the sonar.projectName parameter to the scanner. For example, if you're using the Maven scanner, you would pass mvn sonar:sonar -Dsonar.projectName=YourProjectName.

You can decorate pull requests from multiple ALM instances by creating a configuration for each ALM instance and then assigning that instance configuration to the appropriate projects.

• As part of Developer Edition, you can create one configuration for each ALM.
• Starting in Enterprise Edition, you can create multiple configurations for each ALM. If you have multiple configurations of the same ALM connected to SonarQube, you have to create projects manually.

During pull request decoration, individual issues will be linked to their SonarQube counterparts automatically. For this to work correctly, you need to set the instance's Server base URL (Administration > Configuration > General Settings > General > General) correctly. Otherwise, the links will default to localhost.