Recommended: use an external Continuous Integration tool.
Note: You can use other third-party Continuous Integration tools besides Azure DevOps and Jenkins. However, Talend only focuses on the configuration and pipeline script samples on Azure DevOps and Jenkins documented in these two sections, and the usage of any third-party Continuous Integration tools are out of Talend support scope.
- For an example of CI/CD build using Azure DevOps, see Continuous Integration and Deployment using Azure DevOps.
- For an example of CI/CD build using Jenkins, see Continuous Integration and Deployment using Jenkins.
Alternative: use the Talend Studio Publish option or Talend CommandLine. For more information, see the Talend Studio User Guide.
- ESB use case: For an example of Docker build with ESB artifacts (Data services and Routes Microservices), see Building Docker images for Data Services and Routes Microservices.
In a continuous integration environment, it is common practice to launch tests at every commit. By default, a new commit is made every time you save artifacts.
The following sections introduce two ways to automate the test executions using the Talend CommandLine and Talend Maven plugins to generate the sources, as well as a CI server (Azure and Jenkins) that use build pipelines to automate the execution of all project artifacts and to publish them to an artifact repository or a Docker container.
Talend Continuous Integration is Maven-compliant, which means that you have the possibility to use the Talend Maven commands with any stable version of your Continuous Integration server (Jenkins, Bamboo, etc.).
In case you want to use your own Continuous Integration tool to schedule the execution and publishing of artifacts, Talend allows you to do so by providing you the Talend CI Builder maven plugins.
Talend CI Builder is a Maven plugin delivered by Talend that transforms the Talend Job sources to Java classes using the Talend CommandLine application, allowing you to execute your tests in your own company Java factory. It is available in your license email and can also be downloaded from the Continuous Integration (CI) for cloud section of the Downloads page of your Talend Cloud account.
Starting from version 7.2 onwards, Talend CommandLine is automatically downloaded from the Talend update site and installed during build time to generate and execute your project artifacts. For more information, read Talend CI zero install workflow.
Talend CI Builder may get upgraded upon the installation of a Talend Studio monthly update provided by Talend. You must use the Talend CI Builder version which is compatible to the Talend Studio version in your CI commands or pipeline scripts. To know the exact version of Talend CI Builder you must use, see the changelog corresponding to the Talend Studio monthly update you are using. For more information about the changelog for each Talend Studio monthly update, see Talend Release Notes.
If you encounter an exception on the artifact org.talend.ci:builder-maven-plugin:jar:8.x.x not being downloaded while using Talend CI Builder, and
- if you are using version 7.3.10 or above, make sure the
maven_settings.xml file points to the official plugin
<pluginRepository> <id>central-talend</id> <name>central-talend</name> <url>https://talend-update.talend.com/nexus/content/repositories/libraries/</url> <layout>default</layout> </pluginRepository>
- if you are using Nexus, you can deploy its new version automatically by logging in any project in Talend Studio.
- if you are not using Nexus, you can install its new version to target maven repository manually.