Monitoring the execution of your Jenkins pipeline - 7.3

Talend Software Development Life Cycle Best Practices Guide

Version
7.3
Language
English (United States)
Product
Talend Big Data
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Module
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend JobServer
Talend Studio
Content
Administration and Monitoring
Deployment
Design and Development

Before you begin

Procedure

  1. From the Jenkins home page, select TalendSimplePipeline.
  2. Click Open Blue Ocean in the left panel.
  3. 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 Talend Cloud Management Console: example of Job and Route artifacts with version 0.1.0 deployed in the ci-workspace workspace of the dev-ci environment:
  • in your artifact repository: example of Job and Route artifacts with version 0.1.0 deployed in the Nexus maven-releases repository with an org.talend.ci Group ID:
  • in your Docker registry: example of Job artifacts with version 0.1 and latest pushed to a Docker image called ci_image: