I upgraded to Talend with build TOS_DI-20150702_1326-V6.0.0 I am using it on Ubuntu 14.04 When I try to build job, I do not see the zip file being generated in the given location. Building job does not give any error, just the built is not generated. Please help look into it. Thanks, Neil
Hi Neil,
We are making an investigation on this issue.
Please take a look at a jira issue:
https://jira.talendforge.org/browse/TDI-33318 Could you please take a try on Talend 6.1.0M to see if this issue repro?
Best regards
Sabrina
hi all,
great if it's work in 6.1.0M but not use in Production as it's a milestone.
You could have some surprises as it a none stable version
regards
laurent
Indeed you're right, Laurent.
We should be clear that Milestones should only be used in development environment. 6.0.1, which will be released soon, should include this fix too and thus will provide a real solution for users using 6.0 for their prod environment.
Elisa
Hello Sabrina,
I am experiencing the same error as Neil. We had some jobs generated with an older version (5) and successfuly imported in the new version (6). However when trying to build those jobs, without an error message, job is not built.
Testing parameters:
Windows 7
jdk1.8.0_45
Data integration (both tested):
TOS_DI-20150924_1412-V6.1.0RC1
TOS_DI-Win32-20150908_1633-V6.0.1
Thanks in advance,
Aleix
Hi Aleix,
Are you using 64 bit JDK 1.8 and 64 bit Win7?
A number of reasons can cause a job building to fail.
Could you please check maven setting firstly?
TalendHelpCenter:Failed to build a Job - maven setting Is there any error information(Windows-->ShowView-->General-->Error log)?
Best regards
Sabrina
We are having the same problem with TOS_DI-20150908_1633-V6.0.1 on Mac OS 10.10.5.
This was working earlier this week, but today it doesn't build without any error messages. This is critical for us because this will old up code releases.
UPDATE:
I found these links on a separate post
https://help.talend.com/search/all?query=Failed+to+build+a+Job+-+routine+not+compiling&content-lang=... I turns out I had a compilation problem in a routine
completely unrelated to the job I was building. Ugh.
