Deploying to QA and Production environments for Cloud - Cloud - 7.3

Talend Software Development Life Cycle Best Practices Guide

Talend Big Data
Talend Big Data Platform
Talend Cloud
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Talend Administration Center
Talend Artifact Repository
Talend Cloud Management Console
Talend CommandLine
Talend JobServer
Talend Remote Engine
Talend Studio
Administration and Monitoring
Design and Development
Last publication date
Available in...

Cloud API Services Platform

Cloud Big Data

Cloud Big Data Platform

Cloud Data Fabric

Cloud Data Integration

Cloud Data Management Platform

In Talend Cloud Management Console, the only tool needed to pass artifacts from one environment to another is the Talend Cloud Public API.

In Talend Cloud Management Console, environments are self-contained spaces with the required resources (connections, engines, and so on) that allow the execution of Flows in isolation, with no impacts on other environments. Therefore, executions in the QA environment must not impact executions happening in the Production environment.

Talend allows you to create promotion pipelines using Talend Cloud Management Console or Talend Cloud Public API. These pipelines promote your cloud artifacts from a source to a target environment. For more information on the Talend Cloud API, see Talend Cloud Management Console User Guide.

Best practice: Once a feature is released or a bug is fixed, the best practice is to use 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, validated, and to identify the environment used to make the feature work (CommandLine/Job versions, project properties etc.).