Creating the Jenkins pipeline

Creating 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

How to create the build pipeline on the Jenkins server.

Give a name to the pipeline and select Pipeline in the list.

Pipeline name (example)	Goal
`Talend_Pipeline`	Gets the sources (potentially at each commit) and converts them to Java classes. This project installs and uses the Talend CommandLine application that generates all the sources of the artifacts (Jobs, Routes, Services and Tests) you have created in your project. Runs all Test Cases at once. Deploys the artifacts on the artifact repository or Docker registry of your choice. Warning: To publish ESB artifacts (Routes and Data Services) to Docker, see Building Docker images for Data Services and Routes Microservices.

Pipeline name (example)

Goal

Talend_Pipeline

Gets the sources (potentially at each commit) and converts them to Java classes. This project installs and uses the Talend CommandLine application that generates all the sources of the artifacts (Jobs, Routes, Services and Tests) you have created in your project.
Runs all Test Cases at once.
Deploys the artifacts on the artifact repository or Docker registry of your choice.

Warning: To publish ESB artifacts (Routes and Data Services) to Docker, see Building Docker images for Data Services and Routes Microservices.