More information about deployment identifiers - 7.2

Talend Software Development Life Cycle Best Practices Guide

Version
7.2
Language
English (United States)
Product
Talend Big Data
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Module
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend JobServer
Talend Studio
Content
Administration and Monitoring
Deployment
Design and Development

This section describes the identifier (GroupID) syntax used when deploying artifacts created from Talend Studio.

This syntax applies from version 7.1 onwards. Versions of Talend Studio prior to 7.0 were not fully Maven-compliant, so the syntax rules were adapted to avoid any naming conflicts during deployment.

Deployment identifiers syntax

In this table, <base_groupId> refers to org.example.<project_name> where <project_name> is the name given to your Talend project.
Artifact to be deployed GroupID syntax Example
Project <base_groupId> org.talend.CICD
Bean <base_groupId>.bean org.talend.CICD.bean
Routine <base_groupId>.code org.talend.CICD.code
Joblet <base_groupId>.joblet org.talend.CICD.joblet
Big Data Batch Joblet <base_groupId>.sparkjoblet org.talend.CICD.sparkjoblet
Big Data Streaming Joblet <base_groupId>.sparkstreamingjoblet org.talend.CICD.sparkstreamingjoblet
Standard Job/Big Data Batch/Big Data Streaming <base_groupId>.job org.talend.CICD.job
Route/Routelet <base_groupId>.route org.talend.CICD.route
Service <base_groupId>.service org.talend.CICD.service

Additional configuration about GroupIDs

From the Talend Studio toolbar, you can click the Project Settings icon and open the menu Build > Maven > Deployment GroupID to change the identifier of your project according to your needs. These options have an impact on the deployed artifact identifiers:
  • Append folder name to GroupID: If you select this option, the folder name you define will impact the following items: Joblets, Big Data Batch Joblets, Big Data Streaming Joblets, Standard Jobs, Big Data Batch and Big Data Streaming Jobs, Routes, Routelets and Services.
    Syntax for artifacts without folders Syntax for artifacts with folders
    <base_groupId> <base_groupId>.<user_created_folder_path>
    Example:

    org.talend.CICD

    Example if the path to your Job is folderA/folderB/folderC, the groupID will be:

    org.talend.CICD.folderA/folderB/folderC

  • Skip base groupID if the item has folder: If you select this option, the <base_groupId> will be ignored for the following items: Joblets, Big Data Batch Joblets, Big Data Streaming Joblets, Standard Jobs, Big Data Batch and Big Data Streaming Jobs, Routes, Routelets and Services.
    Syntax for artifacts without folders Syntax for artifacts with folders
    <base_groupId> <user_created_folder_path>
    Example:

    org.talend.CICD

    Example:

    MyCustomFolderName