Recommended: use an external Continuous Integration tool.
- 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 to Cloud option or Talend CommandLine. For more information, see the Talend Studio User Guide.
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 (GIT commit mode).
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 Talend Cloud using Talend Cloud Publisher or to an artifact repository or a Docker container.
To know more about how to publish the Talend Docker images to the major cloud provider container registries (AWS, Azure and Google Cloud), see this article.
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 and Talend Cloud Publisher 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 Cloud Publisher is a Maven plugin delivered by Talend that allows you to publish
the Jobs created from Talend Studio
directly to Talend Cloud.
Starting from version 7.1 onwards, the Talend Maven plugins are embedded in the Talend Studio local maven repository and installed at the first Talend Studio start-up and thus do not require to be installed separately.
Starting from version 7.2 onwards, the Talend CommandLine is automatically downloaded from the Talend update site and installed during build time to generate and execute your project artifacts.