# Configuring Azure DevOps

## Setting up your environment

* Make sure you have set up your Microsoft Azure DevOps account. Refer to [the Azure DevOps documentation](https://learn.microsoft.com/en-us/azure/devops/get-started/) for installation and general setup.
* Download and extract the archive file [azure-pipeline.zip](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/Content/Resources/attachments/azure-pipeline.zip), that contains these files: azure-pipeline.yml, maven\_settings.xml and sample\_pom.xml.
* Install Java JDK 17, Apache Maven superior or equal to 3.6.3, and set up a Git account on a compatible Azure DevOps version control system (Azure Repos, GitHub, Bitbucket Cloud).
* Depending on where you want to publish your artifacts, set up your artifact repositories (Nexus, Artifactory) and your Talend Cloud account.

Technical requirementsTechnical requirements

| Operating system | CPU | RAM | SSD Disk size |
| --- | --- | --- | --- |
| Windows, Linux, Mac | 4 cores or equivalent | 4GB (minimum) | 50GB (minimum) |

## Creating your Azure DevOps project

1. If you do not have an organization yet on Azure DevOps, create one.
2. Create a project and make it private.

## Creating a variable group

In Azure DevOps you can create a variable group to store values that you want to control (URLs, credentials, etc.) and reuse them in all your pipelines.

Information noteNote: Once you have [created your Azure pipeline](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/creating-azure-build-pipeline "Configure the pipeline script provided by Talend to generate the project items according to the Maven phase you want to achieve and the repository you want to deploy your artifacts to."), go back to this page to check the Pipeline permissions to make sure the pipeline can use this variable group.

1. On the Pipelines > Library page, go to the Variable groups tab.
2. Add a new variable group and give it a name, for example talend\_cicd\_param (this identifier will be used in [the Azure pipeline](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/creating-azure-build-pipeline)).
3. Add the following variables and values to the group:
   * patch\_url: URL of the folder where the cumulative patches can be downloaded for Talend Studio.

     Example: https://update.talend.com/Studio/8/updates/R2025-07

   * talend\_ci\_builder\_version: The version of the Talend CI Builder Maven plugin used to generate POM files, code and build.

     Example: 8.0.20

   * talend\_cloud\_url (to publish artifacts to Talend Cloud): URL of the Talend Cloud service in which you want to deploy your artifacts.

     Depending on your region:

     * AWS Singapore: https://tmc.sg.cloud.talend.com/inventory
     * AWS US: https://tmc.us.cloud.talend.com/inventory
     * AWS EU: https://tmc.eu.cloud.talend.com/inventory
     * AWS APAC: https://tmc.ap.cloud.talend.com/inventory
     * AWS Australia: https://tmc.au.cloud.talend.com/inventory
     * Azure US West: https://tmc.us-west.cloud.talend.com/inventory

   * talend\_cloud\_token (to publish artifacts to Talend Cloud): Personal access token necessary to authenticate to your Talend Cloud account.

   * artifact\_repo\_url (to publish artifacts to an artifact repository): URL of the artifact repository (Nexus, Artifactory, etc.) in which you want to deploy your artifacts.

   ![Variables stored in the Azure DevOps library.](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/Resources/images/azure-devops-variables.png)

## Storing your secure files

In Azure DevOps you can add your custom Maven files as well as your Talend product license or local patches as secure files and then use these files in the CI/CD pipelines.

Before you begin:

* Make sure you have extracted these files from the [azure-pipeline.zip](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/Content/Resources/attachments/azure-pipeline.zip) archive file: [maven_settings.zip](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/Content/Resources/attachments/maven_settings.zip) and [sample_pom.zip](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/Content/Resources/attachments/sample_pom.zip).
* Adapt the maven\_settings.xml file to your environment by replacing the parameter values (Nexus or Artifactory URLs, host names, ports, credentials, etc.) and save your changes.

1. On the Pipelines > Library page, go to the Secure files tab.
2. Click the plus sign to upload the maven\_settings.xml.
3. Click the plus sign to upload your license file. You must have received your Talend license file by email, it is also available in the Talend Studio installation folder that has already been setup.
4. Click the plus sign to upload the sample\_pom.xml file. ![Secure files stored in the Azure DevOps library.](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/Resources/images/azure-devops-secure-files.png)
5. Once you have [created your Azure pipeline](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/creating-azure-build-pipeline "Configure the pipeline script provided by Talend to generate the project items according to the Maven phase you want to achieve and the repository you want to deploy your artifacts to."), go back to this page, click the uploaded files, select Pipeline permissions and make sure the Azure pipeline can use all secure files.