How to proceed when the same Nexus service is configured for different environments

Talend Version     6.4 and 6.3

Summary

One Nexus service is configured for both DEV and PROD environments.
Additional Versions  
Product  
Component  
Problem Description When a Nexus service is configured for both DEV and PROD environments, and Talend shares the patch to install, is it available for both environments? If so, how do you validate and apply the patch to existing Jobs in the PROD environment?
Problem root cause

When a Nexus service is configured for both the DEV and PROD environments, the patch assigned to the account can be seen in TAC for both environments.

 

When you download the patch in the DEV environment, the expected behavior is that patch is not visible in the PROD environment. The patch is available in the Nexus repository.

Solution or Workaround

 

Best practices

Talend Support recommends that after downloading the patch in the DEV environment, you verify that all Jobs are executing as expected and that the patch is successfully being applied to the Jobs (if the patch is Studio-specific).

 

Once the Jobs are verified, you can build and publish them accordingly.

You can create tasks in the PROD environment (in general, Studio is not installed or used in the production environment) by either:

  • Creating an artifact task using the updated Jobs (those saved after applying the patch and verifying) available in the Nexus repository

  • Creating a normal task importing the Zip files in TAC > Job Conductor, which are obtained from the Build Jobs option

Disclaimer: In general, the best practice is to avoid configuring the same Nexus service for both the DEV and PROD environments. Download and verify the patch in the DEV environment, then proceed to the PROD environment.

JIRA ticket number  
Version history
Revision #:
9 of 9
Last update:
‎09-29-2018 12:14 AM
Updated by: