Skip to main content Skip to complementary content

Publishing to an artifact repository

Once created, you can publish your Job, Route, or Service into an artifact repository. This artifact repository allows you to centralize, manage, and register all the items created and to be deployed on your Talend Runtime or Talend Remote Engine.

This feature is not shipped with Talend Studio by default. You need to install it using the Feature Manager. For more information, see Installing features using the Feature Manager.

Information noteWarning: A SOAP data service Job including the tESBProviderRequest component that implements a service operation is not allowed to be published independently. The Job has to be published along with the service which the Job is assigned to.

Before you begin

The connection to your artifact repository has been configured in the Talend Studio preferences. For more information, see Configuring repositories for publishing artifacts.

Procedure

  1. In the Repository tree view, select the item you want to publish into the artifact repository.
  2. Right-click it and select Publish in the menu.
    The Publish wizard opens.
    Publish wizard .
    The settings displayed in the Artifact Information area are read only.
    • If a custom group ID has been specified for the item in the Job or Services view, the Group ID field is automatically filled in with the custom ID.
      Otherwise,
      • If the item is a root node in the repository, the Group ID field is automatically filled in with the default group ID set in the artifact repository preference settings.
      • If the item is not a root node in the repository, by default the Group ID field is automatically filled in with the folder structure. For example: getting_started.movies.

      If needed, customize the group ID for the item in the Deployment tab of the Job or Services view.

    • The Artifact ID field is filled in with the name of the item to publish.

    • The Version field is filled in with:
      • the deployment version set in the Job or Services view of the item or in the Project Settings dialog box.
      • deployment version derived from the version of the item to publish if no deployment version has been set for the item.
    • Depending on whether the snapshot option is enabled for the item in the Project Settings dialog box or the Job or Services view:
      • If the Publish as Snapshot check box is selected, a snapshot version of the item will be published to the Snapshot repository.
      • Otherwise, a release version of the item will be published to the Release repository.
    For more information, see Customizing deployment of a Job, Route or Service and Managing deployment versions of Jobs, Routes and Services.
    Information noteNote: The Export Type options are not available when you publish a Route or a Service.
  3. The <Item> Version (the <Item> is Job, Route, or Service) field is automatically filled with the highest version of the item if more than one version of it is available. Change it by selecting the version you want from the list.
  4. From the Export Type list, select:
    • Standalone Job to publish the Job as a standalone Job.
    • OSGI Bundle For ESB to publish the Job as an OSGI Bundle.
      Information noteNote: This option is available only when your Job contains tRESTClient, tRESTRequestm or tESBComsumer components.
    For more information on export types, see Importing/exporting items and building Jobs and Routes.
  5. Click Next and select the export options based on your needs.
  6. Click Finish to publish your item to the artifact repository.
    A confirmation wizard appears when you choose to publish a Release Version Artifact. Click OK to confirm it.
    Now your item is available as an artifact in the repository and can later on be retrieved for deployment and execution on Talend Runtime or Talend Remote Engine. The features of the item, including the dependencies, are also published.

In this section

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!

Leave your feedback here