Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
Iemrich
Contributor
Contributor

Trying to run 142 jobs using one baseline build

Our team currently has a single large dynamic job that pulls extract configuration data from a database and handles 140+ different extracts. We have the same number of tasks (Normal Tasks) set up in Job Conductor that all point to a particular compiled build/version in Nexus of that dynamic Talend job to handle each extract based on the underlying config data.

The problem we face is when we make a change to the large dynamic job and create a new build, these 140+ tasks in Job Conductor need to all be manually changed to the new version. We used Normal Tasks in Job Conductor because Artifact Tasks in Talend 6.x did not work. 

We are migrating to Talend 7.x. What is the best solution so that we do not need to modify 140+ tasks in Job Conductor to use a different Nexus version? Are there any shortcuts with updates in TAC db, or TAC metaservlet uses, having an 140+ Execution Plans point to a single Job Conductor task, or something else that can help us?

Labels (3)
1 Reply
Anonymous
Not applicable

There is an option for normal tasks and for artifact tasks to 'use latest version'​ moving forward with this option will ensure when changes occur to the job and those changes are pushed to git or an artifact repository then the underlying task in tac will be updated automatically when the task is executed.

https://help.talend.com/r/RK~CAb9nJ1erxR8SrBbKoQ/65So~Pr5yMhtDa6zGao56A

I​ believe you can use the metaservlet command to update all tasks to have this option but would refrain from ever making any changes to the backend database.