Building and Deploying
- Recommended: use an external Continuous Integration tool. A wide range of CI server
technologies is available in the CI domain. Talend CI is
not explicitly tied to any specific one and can run on any platform that supports Apache
Maven 3.x. The chosen CI server technology does not impact how Talend CI
works with Maven. However, following these sections — designed specifically for
implementing CI with Jenkins and Azure DevOps Pipeline — can help save time.
- For an example of CI/CD build using Jenkins, see Continuous Integration and Deployment using Jenkins.
- For an example of CI/CD build using Azure DevOps, see Continuous Integration and Deployment using Azure DevOps.
- For information about other CI servers, you can go to Qlik Learning and read the implementation guides about , AWS CodeBuild, Bamboo, BitBucket, Concourse CI, GitHub Actions, GitLab Runner, TeamCity.
-
Alternative: use the Talend Studio Publish, Publish to Cloud option or Talend CommandLine. For more information, see Publishing to Cloud.
- 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.
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, to Talend Cloud or to a Docker container.
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 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. Talend CI Builder is available in the official Talend repository and can be automatically downloaded and installed during build time to generate and execute your project artifacts.
-
Talend Cloud Publisher is a Maven plugin dthat allows you to publish the Jobs created from Talend Studio directly to Talend Cloud. It is activated by adding the -Pcloud-publisher profile parameter to your CI build. This plugin is automatically available with the 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, or 8.0.4 or above, make sure the
maven_settings.xml file points to the official plugin
repository:
<pluginRepository> <id>central-talend</id> <name>central-talend</name> <url>https://talend-update.talend.com/nexus/content/groups/studio-libraries/</url> <layout>default</layout> </pluginRepository> - if you are using Nexus, you can deploy the new version automatically by logging in any project in Talend Studio.
- if you are not using Nexus, you can install the new version to target the Maven repository manually.