Publish job with child jobs doesn't always take the latest sub-job.

Nine Stars

Publish job with child jobs doesn't always take the latest sub-job.

Hi,

We've discovered some odd behavior when publishing a Talend Job to TIC where it doesn't take the latest version of a child job.

 

Example:

Job_A -> tRunJob -> Job_B

 

If you then modify Job_B, save Job_B, right-click on Job_A and then 'Publish to Cloud', Job_A gets built and published with the version of Job_B BEFORE the modification. If you open Job_A, re-select the tRunJob job to run or any other change for that matter, it seems to re-evaluate which version of Job_B to take. Then when you Publish to Cloud, it takes the latest version of Job_B when publishing Job_A.

 

Regards David
Dont forget to give Kudos when an answer is helpful or mark the answer as the solution.

Accepted Solutions
Moderator

Re: Publish job with child jobs doesn't always take the latest sub-job.

Hello,

Sounds like a bug and a FR.

Could you please create a jira issue about it on talend bug tracker?

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.

View solution in original post


All Replies
Moderator

Re: Publish job with child jobs doesn't always take the latest sub-job.

Hello,

Sounds like a bug and a FR.

Could you please create a jira issue about it on talend bug tracker?

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.

View solution in original post

Nine Stars

Re: Publish job with child jobs doesn't always take the latest sub-job.

Confirmed from Customer Care as a bug.

Regards David
Dont forget to give Kudos when an answer is helpful or mark the answer as the solution.
Moderator

Re: Publish job with child jobs doesn't always take the latest sub-job.

Hello,

We will appreciate it a lot if you could post the related jira link here.

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Eight Stars

Re: Publish job with child jobs doesn't always take the latest sub-job.

I just bashed my head against this exact same problem for a couple of hours before it occurred to me to just try quitting the client and re-loading it, that solved the problem.

 

Can anyone explain what is going on, and why no-one else on my team has had this problem for two years? They all think I'm crazy and refuse to believe me!

 

Also I don't think this topic should be marked as resolved, as there is no resolution in the thread.

Nine Stars

Re: Publish job with child jobs doesn't always take the latest sub-job.

Hi,

 

The only resolution we had was to upgrade our Studio to 7.2.1

 

Thanks

 

Regards David
Dont forget to give Kudos when an answer is helpful or mark the answer as the solution.

2019 GARTNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

Self-service Talend Migration: Moving from On-Premises to the Cloud

Move from On-Premises to the Cloud by following the advice of experts

Read Now

How to deploy Talend Jobs as Docker images to Amazon, Azure and Google Cloud reg...

Learn how to deploy Talend Jobs as Docker images to Amazon, Azure and Google Cloud registries

Blog

Best Practices for Using Context Variables with Talend – Part 4

Pick up some tips and tricks with Context Variables

Blog