Skip to main content Skip to complementary content

Publishing a Service, a Route or a data service Job into an Artifact repository using the CommandLine

About this task

Information noteWarning: This feature has been removed from Talend Administration Center 8.0 onwards. For more information, see Talend CommandLine API in Talend Studio User Guide.
Talend offers you the possibility to publish a Service, a Route or a data service Job into an Artifact repository via the CommandLine.

To publish a Service into an Artifact repository:

Procedure

  1. Launch your CommandLine. For more information on how to launch the CommandLine, see Operating modes.
  2. Connect to your repository with the initLocal or initRemote commands. Example: 
    initRemote http://localhost:8080/org.talend.administrator -ul admin@company.com -up admin

    The parameter values are given as examples and need to be replaced with your actual information (port, credentials). For more information on how to use these commands, see the help provided in the CommandLine.

  3. Connect to your project and branch/tag with the logonProject command. If you do not know the name of your project or branch/tag, type in the listProject -b command first. Example: 
    logonProject -pn di_project -ul admin@company.com -up admin -br branches/v1.0.0

    The parameter values are given as examples and need to be replaced with your actual information (project/branch/tag name, credentials). For more information on how to use this command, see the help provided in the CommandLine.

  4. Type in the following command to publish a Service into the Nexus artifact repository: 
    publishService serviceName --version 0.1 --group myGroup --artifactId myService --publish-version 0.1 
--artifact-repository http://localhost:8081/nexus/content/repositories/releases/ --username admin --password admin123
    You can publish a Route or a data service Job into an Artifact repository in the same way using the publishRoute or publishJob command.

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