More information about deployment identifiers
This section describes the identifier (GroupID) syntax used when deploying artifacts
created from Talend Studio.
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 |
|---|---|---|
| Standard Job/Big Data Batch/Big Data Streaming | <base_groupId>.job | org.example.cicd.job |
| Route/Routelet | <base_groupId>.route | org.example.cicd.route |
| Service | <base_groupId>.service | org.example.cicd.service |
Additional configuration about GroupIDs
From the Talend Studio toolbar, you can
click the Project Settings icon and open the
menu 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
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 – let us know how we can improve!