Deploying to QA and Production environments - Cloud

Talend Software Development Life Cycle for Cloud - Best Practices Guide

Version
Cloud
Language
English (United States)
Product
Talend Cloud
Module
Talend Artifact Repository
Talend Management Console
Talend Studio
Content
Administration and Monitoring
Deployment
Design and Development
In Talend Cloud, the only tool needed to pass artifacts from one environment to another is the Talend Cloud Public API.

In Talend Cloud, 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 and validated, and to identify the environment used to make the feature work (CommandLine/Job versions, project properties etc.).