Retrieving generated artifacts in the QA and Production environments - 7.0

Talend Software Development Life Cycle Best Practices Guide

author
Talend Documentation Team
EnrichVersion
7.0
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 Studio
Once the source artifacts (Jobs, Routes, etc) have been generated and deployed in Nexus, they can be retrieved from the Talend Administration Center web applications installed in the QA and Production environments.

Snapshot artifacts that need to be tested and validated are deployed in the snapshots repository of Nexus, while validated artifacts are deployed in the releases repository of Nexus.

  • In the QA environment, where the artifacts need to be tested:

    The user has to connect to the corresponding project in the Talend Administration Center web application of the QA environment, which is linked to the Studio, in order to retrieve all items previously published to the snapshots Nexus artifact repository in order to execute and validate the desired items.

  • In the Production environment, where Jobs are pre-generated and validated:

    The user has to connect to the corresponding project in the Talend Administration Center web application of the Production environment, which is linked to the Studio, in order to retrieve all items previously published to the releases Nexus artifact repository.

Once you have used the Select Job from Nexus option (recommended), you can see that the main Job properties are complete and read-only. You only need to select the context (if several), the log level to be applied and the execution server you have previously started in order to create an execution task on this Job.

Note that the selected execution server needs to have access to the project (access is defined via the Server Project Authorizations page of the web application).