Available in...Cloud API Services Platform
Cloud Big Data
Cloud Big Data Platform
Cloud Data Fabric
Cloud Data Integration
Cloud Data Management Platform
Data Fabric
You can publish Jobs, Routes, and Data Services (artifacts) created in Talend Studio to
Talend Cloud
and make it available to specific or all users of Talend Management Console.
To publish artifacts from Talend Studio to
Talend Cloud
through Maven, refer to the Talend Software Development Life Cycle Best Practices
Guide.
Before you begin
- Set the account authentications to the web application in Talend Studio.
For further information, see Setting up a remote connection to Talend Management
Console.
- You must have the default Operator role or the
Operations - Manage
Talend Management Console
permission assigned to you in Talend Cloud.
- You must have the Publish: Publish artifacts permission on
the workspace to which you are publishing.
- Make sure the name of your artifact to be published does not contain any reserved
words, such as
SNAPSHOT
, otherwise the publication will fail.
- Make sure that the artifact name is different from any existing task's name across
all the workspaces and environments of the target Talend Management Console
account. If a task with the same name already exists, you risk at unintentionally
updating that existing task when publishing your artifact, without creating the
intended task.
About this task
Once your artifact is published, its corresponding task is automatically created and it
can be run by web users in Talend Management Console. You
can create different tasks from the same artifact to run it in different scenarios by
changing its context parameter values.
Restriction: The artifact published to
Talend Cloud cannot be larger than 400MB.
Procedure
-
In the Repository tree view, right-click a Job, Route, or
Data Service and select Publish to Cloud.
The Publish to Cloud wizard is displayed.
If any of the account authentications to the web application is missing from
Talend Studio,
the Preferences window opens by default, where you can add
the missing information.
If the Stop checking issues when publishing to Talend Cloud
(from R2023-03 onwards) or Skip checking Job commit and
push status (from R2022-01 to R2023-02) check box in the view is cleared, a dialog box pops up to give a warning message in
any of the following cases when publishing to Talend Cloud:
- The Job, Route, or Data Service contains changes not pushed to the
remote Git repository
- The Job or Route contains a context variable of any numeric data type,
whose value does not match its type (from R2023-03 onwards)
Note that if your Job includes any password type context parameter, for security
reasons, its value will be cleared during publication and must be set for the Job
tasks in Talend Cloud.
For more information about the Job tasks in Talend Cloud,
see Creating Job tasks.
In the dialog box, you can change the status of the Stop checking
issues when publishing to Talend Cloud
(from R2023-03 onwards) or Skip checking Job
commit and push status (from R2022-01 to R2023-02) check
box, click Publish anyway to continue publishing, or
click Cancel to terminate the publish process. For
more information, see Connecting Talend Studio to Talend Cloud.
-
In the Publish With Version field, change the version you
want to publish to the cloud if needed.
This field is automatically filled in with the highest version of the artifact, if
several versions are available. You cannot publish an artifact smaller than the
latest published version displayed in the Last Cloud Version
field.
-
If you have installed the 8.0 R2023-06 Talend Studio
monthly update or a later one provided by Talend,
select the environment and the workspace where you want to publish the artifact from
the corresponding drop-down lists.
Otherwise, select the workspace from the Workspace
drop-down list. The workspaces in the drop-down list are organized according to the
environments where the workspaces are created.
-
ⓘAvailable in:
Cloud Big Data
Cloud Big Data Platform
Cloud Data Integration
Cloud Data Management Platform
Select Export Artifact Screenshot to publish a capture of
the Job design to the cloud.
-
ⓘAvailable in:
Cloud API Services Platform
Cloud Data Fabric
Data Fabric
Select an option:
Option |
Results |
Export Artifact Screenshot
|
Publish a capture of the artifact design to the cloud. It is not
possible to publish a SOAP Data Service screenshot to the cloud, as there
are multiple designs for it.
|
Update corresponding job task |
If you have already published a Route or data service, you can choose to
update the tasks it is used in. Only the task with the same name and in the
same workspace as the artifact will be updated in Talend Management Console.
You must deploy the task with the new artifact version before the change
takes effect.
Note: To update Job tasks automatically when publishing a new version, you must
enable the Always use the latest available artifact
version option in Talend Management Console.
|
Enable Prometheus metrics endpoint
|
Build the Prometheus metrics endpoint into the Microservice to monitor the
execution of Jobs or Routes, JVM memory, CPU consumption, and so on. By
default, this feature bridges all the JMX attributes and values into
Prometheus. For more information about Prometheus, see the documentation. Restriction: For Jobs, this option is
applicable from 8.0.1-R2024-03.
|
-
Click Finish.
An information bar is displayed to show the progress of the deployment.
- Optional:
Click Run in Background to continue working in Talend Studio
while the artifact is being published.
A progress bar is displayed in the bottom-right corner of Talend Studio to
show the percentage of the publishing operation completed. Click the progress bar
icon to display the details in the Progress view.
Results
When you publish the artifact, a message is displayed to confirm the publication and to
prompt you to open the corresponding task that was created in the web application. Click
Open Task in the message to open the task in the
Task Details page in Talend Management Console. The
task will have the same name as the artifact.