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 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.Warning: To use this feature, you need to apply the latest 7.2.1 patch. For more information, contact the Talend support.
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 (Automatic SVN or 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 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.