Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Creating the Jenkins pipeline

Configure the pipeline script provided by Talend to generate the project items according to the Maven phase you want to achieve and the repository you want to deploy your artifacts to.

Some parameters come from the credentials and configuration files you have previously defined and stored in Jenkins. For more information about the Talend Maven parameters you can use when configuring your pipeline, see Talend custom Maven build options.

Before you begin

Make sure you have extracted this file from the jenkins_pipeline.zip archive file: Talend_Simple_Pipeline.jenkins .

Information noteWarning: This file is an example and must be adapted to your environment before it is used. It gives you some predefined Maven commands and options that you can customize to fit your deployment needs. For example, the Talend_Simple_Pipeline.jenkins script file allows you to build and publish artifacts to Talend Management Console. If you want to publish artifacts to an artifact repository or to Docker, uncomment the corresponding parameters in the script.

Procedure

  1. Edit and adapt the values in the file according to your environment:
    Information noteNote: All the project variables have been set in the script to simplify the import in Jenkins, but as a good practice, they can be externalized in the Jenkins project and defined as variables in the GUI to update them more easily. To do this, check This project is parameterized? in the general configuration of your project pipeline, add them all then remove them all from the script.
    Parameter Description Example of value
    PROJECT_NAME Talend Project name as it is declared in Talend Management Console or Talend Administration Center. CICD
    GIT_URL URL of the Git repository hosting the Talend project sources. https://github.com/company/cicd.git
    GIT_BRANCH The Git branch to build. main
    JOB_LIST The list of Jobs to build, with comma-separated values. Use the format jobs/process/<PATH>/<name_of_the_job>_<version> for Jobs, and jobs/routes/<PATH>/<name_of_the_route>_<version> for ESB Routes.

    The name of the Job or Route is in lowercase.

    If you need to build the full project, remove the parameter -pl ${JOB_LIST} from the Maven command.

    		 jobs/process/LOAD/hello_world_0.1
    TMC_ENV Talend Cloud environment. DEV
    TMC_WORKSPACE Talend Cloud target workspace. The Talend CI user must have the Publish permission on this workspace. CICD
    PATCH_URL URL of the Talend repository hosting patches and updates (can be remote or local). https://update.talend.com/Studio/8/updates/R2025-07
    TALEND_CI_BUILDER_VERSION Talend CI builder version linked to the patch version. 8.0.20
  2. Comment/Uncomment the build stages corresponding to 'Talend Cloud' or 'Talend on-prem' in the script according to your needs.
  3. From the Jenkins home page, click + New item.
  4. Enter a name for your pipeline, Talend_Simple_Pipeline for example.
  5. Select the Pipeline type.
  6. Click OK.
  7. Copy and paste the updated Talend_Simple_Pipeline.jenkins content into the Script field and apply the changes.

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