Running the Jenkins pipeline - 7.3

Talend Software Development Life Cycle Best Practices Guide

EnrichVersion
7.3
EnrichProdName
Talend Big Data
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
EnrichPlatform
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend JobServer
Talend Studio
task
Administration and Monitoring
Deployment
Design and Development

Before you begin

  • Your artifact repository (Nexus or Artifactory) is started.
  • Your Talend CommandLine is configured and started:
    • Go to the Talend CommandLine directory and open the commandline.bat or commandline-linux.sh according to your Operating system.
    • Edit the -data value with the $WORKSPACE variable to ensure each Jenkins pipeline will use its own dedicated workspace:

      For Linux:

      ./Talend-Studio-linux-gtk-x86_64 -nosplash -application org.talend.commandline.CommandLine -consoleLog -data $WORKSPACE -p 8002

      For Windows:

      Talend-Studio-win-x86_64.exe -nosplash -application org.talend.commandline.CommandLine -consoleLog -data $WORKSPACE -p 8002
    • Start the Talend CommandLine at least once to create the local .m2 repository then close it.
      Note: Starting Talend CommandLine as a server is deprecated.

Procedure

  1. From the Jenkins home page, select Talend_Pipeline.
  2. Click Open Blue Ocean in the left panel.
  3. Click Run.
  4. Click the new line that appears on the list to see the pipeline progress.

Results

The pipeline is launched and your project is being processed according to the Maven phases that have been defined in your script. 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.

You can see their results displayed:

  • in Jenkins: the detail of your results can be found in the logs that you can display by clicking the Display the log in new window icon.
    Example where you can see the successful execution of the test named test_feature903:
  • in your Nexus web application or Artifactory: example of Jobs and Services artifacts with version 0.1.0 deployed in the releases repository with an org.talend.cicd Group ID:
  • in your Docker registry: example of artifacts with version 0.1 (image tag) pushed as a cicd Docker image in an Artifactory Docker registry: