.bat and .sh launcher files missing / not created with Build Job

[billimmer]

Greetings,
I am new and trying Talend Open Studio for MDM 5.6.2 on a Windows desktop PC.  I have created several test jobs that I would like to schedule to run on a Windows or Linux server.  I use the Build Job, with Shell Launcher checked and set to "All".  But .bat and .sh files are not created.  
Is there some trick to this I am missing?
Thanks much!

[Anonymous]

Hi,
Can you execute your test jobs successfully in studio? Did you follow up document:https://help.talend.com/display/TalendOpenStudioforMDMUserGuide56EN/5.2.2+How+to+build+Jobs to build your job as a Standalone Job?
Best regards
Sabrina

[billimmer]

Yes, the job runs great in studio.  I am following the example where the current date and time is written to a file using the tFixedFlowInput and the tFileOutputDelimited.  
I am using Standalone job.  Image is below.  

I've tried many times.  Here are the files created:

Thanks for your response.

[_AnonymousUser]

I am seeing the exact same issue on Talend 5.6.1.20141207_1530

[Anonymous]

Hi,
Have you tried to uncheck option "Extract the zip file" to see if it works? We cannot repro this issue on our side.
Best regards
Sabrina

[billimmer]

Unchecking the zip doesn't help for me.  I am running 
Build id: V5.6.2_20150508_1414, with 
eclipse.launcher.name=TOS_MDM-win-x86_64
java.version=1.7.0_79

[billimmer]

I have installed 6.0.1 with jdk1.8.0_60.  I create a new workspace and test job.  The job just has one "hello world" tjava and it runs without error.
In this release, the build job appears to run and does not give an error.  But the .zip is never created.  I don't get anything in the specified directory.
Any thoughts?

[billimmer]

At last!  This looks like a version 5.6.2 problem/bug when your workspace is a Windows UNC path...
Tests:
Test #1 - Create new workspace, project and job on local C: drive.  Jar and launcher files created...
Test #2 - Create new workspace, project and job on UNC path.  Jar, but no launchers...
Test #3 - Copied Test #1 workspace to Test #2 UNC path.  Opened workspace and project, and ran the job ok.  But no launchers on build...
NOTE:  All three tests were built to a C: path
I'm going to test on 6.0.1 to see if this is also the problem with no build files.  I'll post results to the missing build thread...

[_AnonymousUser]

Hey ! 
i am also facing the same issue.did any one get any solutions ?

[billimmer]

Is your workspace on a windows network drive - where you are connecting by UNC path or mapped drive?  From my testing, no launcher files will be created if the workspace is on a windows share.  Test using a new workspace on your local C: drive.