Continuous Integration: Deploying to QA and Production environments - 6.5

Talend Software Development Life Cycle Best Practices Guide

author
Talend Documentation Team
EnrichVersion
6.5
EnrichProdName
Talend Big Data
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
task
Administration and Monitoring
Deployment
Design and Development
EnrichPlatform
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend JobServer
Talend Repository Manager
Talend Studio
In a Production environment, the only tools needed are:
  • the Talend Administration Center application to schedule the execution of the Jobs,

  • an execution server, to deploy and execute the Jobs,

  • Talend Repository Manager to pass items to the QA and Production environments.

The Job generation step is indeed skipped as Talend Administration Center is able to retrieve pre-generated Jobs from archive files. The Talend CommandLine application is thus no longer needed.

Likewise, the Production environment does not require to be linked to SVN or GIT as the Jobs that were pre-generated in the previous environments can be imported and executed in a "no-storage" project.

Best practice: Once a feature is released or a bug is fixed, the best practice is to use SVN or GIT branches and tags to record this change of status. They are used to identify a specific version of a project at a given time, for example the feature that has been developed, tested and validated, and to identify the environment used to make the feature work (CommandLine/Job versions, project properties etc.).