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

Using YAML or the Azure Classic editor to create the Azure build pipeline for JavaScript, TypeScript, Go, Python, PHP, and other projects.

This page explains how to add the SonarQube Community Build analysis to your Azure build pipeline for projects that are not Maven, Gradle, or .NET.

Before you begin, see the Azure Pipelines integration overview page.

Once you have created and set up your SonarQube Community Build project, check out the Creating and configuring your project and Setting up project integration pages for information about adding the SonarQube analysis to your Azure build pipeline.

To create your Azure build pipeline, you can use either YAML or the Azure Classic editor.

• The use of the Classic editor is not always possible (e.g. if your code is stored on GitHub).

• If you use YAML, Sonar can provide you with YAML templates or code examples.

If you need to use a specific scanner version, see the Using various features page.

Using YAML

Add the following SonarQube tasks to your YAML pipeline:

1. Before your build task, add a Prepare Analysis Configuration task.

2. After your build task, add a Run Code Analysis task.

3. After the Run Code Analysis task, add a Publish Quality Gate Result task.

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

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

Using the Classic editor

In the procedure below, the manual configuration mode is used to define analysis parameters at the pipeline level. You may use the sonar-project.properties file instead (or another specified configuration file). For more information, see the Using various features page.

Proceed as follows:

1. In the Azure DevOps’ Classic editor, create or edit your build pipeline.

2. Add a Prepare Analysis Configuration task before your build task:

   • In SonarQube Service Endpoint, select the SonarQube Server service connection you created during setup. See the Setting up project integration page for more information about adding a connection.

   • Under Choose a way to run the analysis, select Use Standalone SonarScanner CLI.

   • Select the Manually provide configuration mode.

   • In the Project key field, enter your project key.

3. Add a new Run Code Analysis task after your build task.

4. Add a new Publish quality gate Result on your build pipeline summary.

5. 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 Community Build analysis to run automatically.

6. Save your pipeline.

Related pages

• Gradle or Maven project

• .NET project

• Using various features when adding the analysis to your pipeline

• Quality gate status in release pipeline

• SonarQube tasks for Azure Pipelines