Skip to main content Skip to complementary content

Configuring Azure DevOps

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, 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.
  3. Add the following variables and values to the group:
    • This parameter is only supported and needed for users with Talend Studio 8.0.1 R2024-04 or lower:

      p2_base_url: URL of the P2 server that contains the Talend CommandLine as well as the Maven plugins necessary to generate and deploy your artifacts. See Before scheduling the execution of your artifacts for an example of how to host the P2 archive on Tomcat.

      Example: https://update.talend.com/Studio/8/base

    • p2_update_url: URL of the folder where the cumulative patches can be downloaded.

      Example: https://update.talend.com/Studio/8/updates/R2023-02

    • talend_cloud_url (to publish artifacts to Talend Cloud): URL of the Talend Cloud service in which you want to deploy your artifacts.

      Example: https://tmc.eu.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_url (to publish artifacts to an artifact repository): URL of the artifact repository (Nexus, Artifactory, etc.) in which you want to deploy your artifacts.
    • docker_registry (to publish artifacts to Docker): URL of the Docker registry in which you want to deploy your artifacts.
    • docker_image_name (to publish artifacts to Docker): Docker image name inside the Docker registry in which you want to deploy your artifacts.
    • docker_username (to publish artifacts to Docker): User name necessary to authenticate to your Docker registry.
    • docker_password (to publish artifacts to Docker): Password necessary to authenticate to your Docker registry.

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:

  • Download and extract these files:
  • Retrieve the CI Builder plugin archive, either from your license email, or from the Continuous Integration (CI) for cloud section of the Downloads page of your Talend Cloud account.
    Information noteNote: Storing Talend CI Builder 8.0.4 or higher in Azure DevOps is optional. Starting from Talend CI Builder 8.0.4, it is available in the official Talend repository, which is referenced in the maven_settings.zip file.
  • 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.
    Information noteTip: This example file is adapted for Nexus. If you are using another artifact repository like Artifactory, you need to adapt this example to your repository URLs.
  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.
  4. Click the plus sign to upload the Talend-CI-Builder-Maven-Plugin-20211109_1610-V8.0.x.zip CI plugin that you downloaded from your Talend Cloud account.
  5. Click the plus sign to upload the sample_pom.xml file.
  6. Once you have created your Azure pipeline, go back to this page, click the uploaded files, select Pipeline permissions and make sure the Azure pipeline can use all secure files.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!