Before configuring the execution of your Jobs - 6.5

Talend Software Development Life Cycle Best Practices Guide

Talend Documentation Team
Talend Big Data
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Administration and Monitoring
Design and Development
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend JobServer
Talend Repository Manager
Talend Studio
There are several prerequisites you should ensure before you start scheduling automatic test executions with the Talend CI Builder.
  • A version superior or equal to Apache Maven 3 is installed in your server. For more information, see the Apache Maven website.

  • The Jenkins Continuous Integration server is properly installed and set up. For more information, see the Jenkins website.

  • You have a Talend CommandLine application that will only be used for Continuous Integration purposes (cannot be the same as the Talend CommandLine used for generic actions such as publishing items from Talend Studio to Talend Administration Center, generating execution tasks in Talend Administration Center, etc.).

  • You have previously created Test Cases in your SVN or Git project that you want to execute automatically. For more information, see Designing Tests.

  • The external libraries stored in Nexus that are needed to execute your Jobs have been properly installed in this project and your Nexus instance is started. .
    • If you are using Talend Administration Center, you have configured it to retrieve the external modules from Nexus.

    • Otherwise, you need to configure the CommandLine to connect to the Nexus repository where these external modules are stored by editing the <StudioPath>/configuration/config.ini file and adding the following at the end of the file:

      where <http://localhost:8081/nexus> corresponds to your Nexus location URL, and <Nexus_username>/<Nexus_password> corresponds to your Nexus credentials.

      By default, only the nexus.url value is mandatory, as nexus.user and nexus.password values are not needed to download the modules.

  • In order for the deployment to Nexus to work, you need to add the following in the /.m2/settings.xml Maven configuration file:

    For more information on this file, see the Apache Maven documentation.

To summarize, you need the following applications: Talend CommandLine, a Continuous Integration server (here, Jenkins), Maven, Nexus and Talend CI Builder.