Implementation in your environment - 7.0

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 Studio

The following diagram shows how Talend tools can be used and integrated in your own Java fabric, ensuring quick integration and quality of your projects from the beginning to the end of your software life cycle.

Warning: The content of this document also applies to ESB (Routes and Data Services). However, note that the use of the CI Builder for ESB purposes is in TECHNICAL PREVIEW in this version and it is recommended to use the Talend CommandLine commands to build and publish Routes and Data Services in a production environment.
The main phases of the Continuous Integration process that are presented in this diagram are the following:
  • 1 and 2 (Git or Subversion): Version and Revision Control

    Committing: Developers design Jobs and Tests in Talend Studio and commit them to Git or Subversion.

    Checking out sources: Git and/or SVN are linked to the Continuous Integration server that checks out the Jobs and Tests sources in the form of .item and .properties files as well as the corresponding pom.xml files pregenerated by the CommandLine.

  • 3 to 6 (in external Java factory): Maven Build, Continuous Integration and Deployment

    Generating sources: The Talend CI Builder and Talend CommandLine tools generate the Git/SVN sources and pass them to the Continuous Integration server that is used (Jenkins for example).

    Compiling sources : An automated build is launched on the server to compile sources (transformed to Java classes).

    Testing: Automated builds are launched on the server to execute Tests, and the server dashboard allows you to monitor and audit code quality before packaging.

    Packaging and publishing: Once the Tests are executed and the bugs are fixed, items are packaged and published in the Nexus Artifact repository (in the form of .zip files). The versioned release candidate is then deployed to Production.

Continuous Integration ensures a quick, effective, automated and safe deployment to Production.