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

[David_Beaty]

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.

[Anonymous · Accepted solution]

Hello,

Sounds like a bug and a FR.

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

Best regards

Sabrina

[David_Beaty]

Confirmed from Customer Care as a bug.

[Anonymous]

Hello,

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

Best regards

Sabrina

[PhilHibbs]

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.

[David_Beaty]

Hi,

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

Thanks