Creating a variable group in Azure DevOps - Cloud - 7.3

Talend Software Development Life Cycle Best Practices Guide

Version
Cloud
7.3
Language
English
Product
Talend Big Data
Talend Big Data Platform
Talend Cloud
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend JobServer
Talend Management Console
Talend Remote Engine
Talend Studio
Content
Administration and Monitoring
Deployment
Design and Development
Last publication date
2024-02-08
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.

Procedure

  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:
    • updatesite_path: 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.
    • 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_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.
  4. Make sure the Allow access to all pipelines toggle is enabled and save.