Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
WLawton
Contributor
Contributor

Best practice for Nexus with multiple contexts

We have a job that runs exactly the same for each of 20 contexts. If we create the task from svn, we can create an instance of the job and choose a specific context for each instance. That is, one job, 20 copies. Each job has its own context and schedule. With Nexus, we are required to choose a specific context when we publish the job. We are not able to select or change the context when we create an artifact task in job conductor. We want to use Nexus. What is the "best practice" for using Nexus but allowing us to create multiple instances of the same job?

Labels (3)
1 Reply
Anonymous
Not applicable

Hello,

Here is a KB article about: https://community.talend.com/s/article/Best-practices-for-deploying-Talend-Jobs-and-Frequently-Asked...

Actually, there wasn't a real clear best practice, which is understandable since it depends on the project.

Would you mind creating a support case on talend support portal so that we could give you a remote assistance to see if there is a good way for your job?

Best regards

Sabrina