Issue building package

[tOmoness]

When Jenkins tries to execute the ISCmdBld executable I get the following error: 'C:\Program' is not recognized as an internal or external command

My path for ISCmdBld.exe is: C:\Program Files (x86)\InstallShield\2012\System\ISCmdBld.exe

[conyx]

Hi Tom,

could you please provide us the whole Job console output, especially the line starts with "Executing command: ..."

TB

[tOmoness]

Executing command: "C:\Program Files (x86)\InstallShield\2012\System\ISCmdBld.exe" -p "C:\Jenkins\workspace\InstallShield Projects\Customer Packages\MyProject.ism" & exit %%ERRORLEVEL%%
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
ISCmdBld.exe ERRORLEVEL code: 9009
Build step 'Execute InstallShield builder' marked build as failure

[conyx]

Have you tried to paste
"C:\Program Files (x86)\InstallShield\2012\System\ISCmdBld.exe" -p "C:\Jenkins\workspace\InstallShield Projects\Customer Packages\MyProject.ism" & exit %%ERRORLEVEL%%
manually into the Windows command line tool (cmd.exe) and run it? Does it work?

[tOmoness]

Yeah and it works fine.

[conyx]

Well, I am not able to reproduce this bug. InstallShield plugin just passes this command into the shell, which is "cmd.exe" in that case, so it should show the same behaviour.
You can try to use a simple batch builder for this purpose although it's not a nice solution.

[conyx]

Well, I have finally found the bug! The problem is caused by the space sign inside the project file path (...Customer Packages...). New version of IS plugin will be released ASAP!
Thanks for the report. ;)

[tOmoness]

Fantastic news! I was just using a .bat file for the time being, but well done on finding the issue. I'll update once released. Thanks again.