Migrating from Talend CI version 6.x to 7.0

Migrating from v6.x to v7.x

Starting from version 7.x onwards, several improvements have been made to automate and ease the process of building Talend Jobs and projects.

If you have used the Talend Continuous Integration features previously, you might want to compare the old and new processes.

Differences between building Jobs and projects in v6.x and v7.0

Subscription

Steps to reproduce to execute, publish and deploy your project items
Before 7.0	In version 7.0
Using Talend Administration Center: From the Publisher page, create a task on the Job/Jobs/Project you want to publish on Nexus. From the Job Conductor page, retrieve the task from the Publisher or directly from Nexus to schedule the Job executions through time-based triggers.	Same process as in previous versions but using Talend Administration Center Publisher is not recommended (deprecated). See Option 2: Publishing and scheduling test execution in Talend Administration Center for more information.
Using Talend CI Builder combined with an execution server (Jenkins for example): Complete the prerequisites. Refer to the documentation provided for your version for more information. Install Talend CI Builder and upload it into the thirdparty Nexus repository that exists by default. Refer to the documentation provided for your version for more information. Create three build projects on Jenkins: one build to get the sources and converts them to Java classes with the Talend CI Builder, one build to run all Jobs and Tests at once and one build to deploy project artifacts on Nexus. Refer to the documentation provided for your version for more information. Configure these build projects: link them to your Git/SVN project decide how to generate sources, either locally (recommended) or remotely (script mode). It is recommended to create a POM file holding Maven project information and instructions to generate the sources. You also have the possibility to control the deployment version value from Talend Studio. Refer to the documentation provided for your version for more information. specify all the parameters needed to build, including the filters to only build the project items you want using the <itemfilter> parameter. Example of filter applied to execute all Standard Jobs located in the subfolders with a name starting with `Export` under the MainProcess folder: `-DitemFilter=(type=process) and(path%MainProcess/Export*)` Refer to the documentation provided for your version for more information. Make sure your Talend CommandLine application points to the Jenkins workspace where your project sources are stored then build the three projects. The packaged artifacts will be published on the Nexus repository specified in the POM file you have created. Refer to the documentation provided for your version for more information.	Using Talend CI Builder combined with an execution server (Jenkins for example): Complete the prerequisites, including editing the maven_user_settings.xml file to add connection information to Nexus. See Before configuring the execution of your Jobs. Install Talend CI Builder, create a thirdparty Nexus repository (does not exist by default) and publish it to this new repository. See Installing Talend CI Builder and uploading it on Nexus for more information. Create one unique build project on Jenkins that will generate the sources, run alls Jobs and associated Tests and deploy them to the Nexus repository of your choice. See Creating the Jenkins project for more information. Configure this build project: link it to your Git/SVN project decide how to generate sources, either locally (recommended) or remotely (script mode). No need to create a POM file as POM files are automatically pre-generated for every project item. However you can change both the deployment identifier of the project (groupID) and the deployment version values from Talend Studio. See How to change the deployment identifier of the project at once for more information. specify all the parameters needed to build. The <itemfilter> parameter no longer exists as you can use directly the Maven compliant parameters in the Jenkins build configuration to build the project items you want. Example of Maven command used to clean the project build directory (deleting old files), launch the generation of the Job named `job_feature400` as well as its related Test cases and dependencies and package the Java code in an output file (.jar, .zip): `mvn clean package jobs\process \job_feature400_0.1 -am` See How to filter the execution of your project on selected Jobs using Maven for more information. Make sure your Talend CommandLine application points to the Jenkins workspace where your project sources are stored then build the Jenkins project with parameters to select in which Nexus repository the artifacts will be published. See Building the Jenkins project for more information.