Building the Jenkins project - 7.0

Talend Software Development Life Cycle Best Practices Guide

Talend Documentation Team
Talend Big Data
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Administration and Monitoring
Design and Development
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend JobServer
Talend Studio
How to build the project on Jenkins using the proper parameters.

Before you begin

You have defined all the parameters necessary to build your project artifacts, see Specify the parameters to generate and deploy the sources.


  1. Make sure your Talend CommandLine application points to the Jenkins workspace where your project sources are stored:
    • If you installed Talend CommandLine as a service on Windows, you need to go to the service installation directory and open the file <service_path>/conf/wrapper.conf to edit the parameter value and point to the Jenkins workspace where your project sources are stored.
    • If you installed Talend CommandLine as a service on Unix, you need to edit the file that calls the service script.
    • If you did not install Talend CommandLine as a service, edit the .bat or .sh file of Talend CommandLine to change the data parameter value.
  2. Start the Talend CommandLine service.
  3. From the Jenkins home page, select the Generate_Execute_Deploy project.
  4. Click Build with parameters in the left panel.
  5. In the list, select the parameters to build your project and execute the Maven phase of your choice.
    Tip: If you are building your project for the first time, you can select generate-sources to only test the generation of your source code.
  6. If you have selected the deploy phase in the list, you have to select the Nexus repository in which you want the packaged artifacts to be deployed.
  7. Click Build.


The build is launched and your project is being processed according to the Maven phase that has been defined.

The best practice is to use the deploy phase in order to generate the source code, compile it, test it, package it and then deploy the packages into Nexus.

You can see their results displayed:

  • in Jenkins: the detail of your results can be found in the Console Output view of the specific builds.
    Example where you can see one failure on the execution of the test named test_process_client_file):
    Example where 6.3.1-SNAPSHOT artifacts are being deployed to the TALEND group in the repository):
  • in Jenkins: a diagram that represents graphically the status of the last executions of the project (here you can see one failure out of a total of six tests):
  • in your Nexus web application: you can find the artifacts deployed in the defined repository: