Building a Job using the CommandLine

About this task

Building a Job allows you to generate an archive of a specific Job along with all of the files required to execute the Job, including the .bat and .sh as well as any context-parameter files or other related files. This archive can then be used to deploy and execute the Job on a server without having to generate it via the CommandLine first.

Procedure

Launch your CommandLine. For more information on how to launch the CommandLine, see Operating modes.
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.
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.
(Optional) If you are using user components, copy them in a folder on your CommandLine server, then type in the following command with the path to this folder:
```
setUserComponentPath -up C:/components
```
The parameter values are given as examples and need to be replaced with your actual information (folder path). For more information on how to use this command, see the help provided in the CommandLine.
Type in the following command to build your Job archive in the folder of your choice:
```
buildJob MyJob -dd C:/tac/builds -af MyJob_0.1 -jc Default -jv 0.1
```
The parameter values are given as examples and need to be replaced with your actual information (Job name/context/version, target archive directory, archive name). In this example, a Job named MyJob is built in the archive named MyJob_0.1.zip, in the C:/tac/builds folder. The best practice is to put the archive file in the Job archive folder, which path is defined in the Job Conductor node of the Configuration page.

For more information on how to use this command, see the help provided in the CommandLine.

You can build a Route in the same way using the buildRoute 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