Configuring Jenkins to run all tests - 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
How to configure the RunTests project on Jenkins to execute all Tests available in your project.

Before you begin

You have created and configured the GenerateSources Jenkins project to retrieve the sources of your Jobs and Tests, see Creating the Jenkins projects and Configuring Jenkins to generate the sources.


  1. In the RunTests project configuration, set the path to the <jenkins_workspace>/RunTests/projectSources/pom.xml file generated previously in the Root POM field of the Build area.
  2. In the Goals and options field, enter the Maven instruction run all Tests.
    test -fn -e

    This Jenkins project retrieves the POM file generated during source generation and use it to run all available Test Cases.

  3. In the Advanced part of the Build area, select Settings file in filesystem in the Settings file list and point to the Maven settings file of the Studio with all the dependencies needed to run all Tests.
  4. (Optional) Add a post-build action to trigger the DeployToNexus build. Note that, if you add this step, artifacts will be deployed automatically to Nexus after Test executions following default instructions (default groupID, default version, etc.) held in the source POM file. These default values can be edited through the Studio project settings before generating the sources and their corresponding POM file.