Creating the Jenkins pipeline

How to automatically create the build pipeline on the Jenkins server following the configuration defined in an XML file.

Before you begin

The jenkins_pipeline_simple.xml file has been retrieved from the Downloads tab of this page.
The Talend_Full_Studio_p2_repository--YYYYYYYY_YYYY-VA.B.C.zip archive has been downloaded. You can either extract it to a folder on the build server or host it on an HTTP server as described in Before scheduling the execution of your artifacts. The path or the URL is used to configure the -Dupdatesite.path parameter in the jenkins_pipeline_simple.xml file.
The archive of the patch you want to install, for example, Patch_20220513_R2022-05_v1-7.3.1.zip, has been downloaded and placed on the build server. The path to the patch is used to configure the -Dpatch.path parameter in the jenkins_pipeline_simple.xml file.

Look for the XXX references in the jenkins_pipeline_simple.xml file and replace them with the values corresponding to your environment.
Note that you must use the Talend CI Builder version which is compatible to the Talend Studio version in your CI commands or pipeline scripts. To know the exact version of Talend CI Builder you must use, see the changelog corresponding to the Talend Studio monthly update you are using.
Open a command prompt window, browse to the folder where the jenkins_pipeline_simple.xml is located and execute the following Curl command to automatically create your pipeline:
```
curl --location -g --request POST --header "Content-Type: application/xml" --data-binary @jenkins_pipeline_simple.xml -u <jenkins_username>:<jenkins_token> <jenkins_url>/createItem?name=TalendSimplePipeline
```
Information noteNote: Make sure you replace the <jenkins_username>, <jenkins_token> and <jenkins_url> with the values corresponding to your environment (username and API token needed to authenticate to Jenkins, and Jenkins server URL).
Click OK to confirm the pipeline creation.

The new pipeline named TalendSimplePipeline is displayed on your Jenkins dashboard.

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!