"execute command" environment?

Deadline
1

Hi there!

Using the “execute command” remote works fine for normal commands like ‘dir’, etc. on our Win7 renderfarm. But now I wanted to use the “choco” command of the chocolatey app (www.chocolatey.org), to remotely install tools on all the renderfarm machines. Via RDP I can just start a “cmd” window and use the “choco” command, which is installed to ‘C:\ProgramData\chocolatey\bin\choco.EXE’. When using it via Dealine’s ‘execute command’ like this ‘cmd /C choco’, I always get the error message:

Command Stderr: ‘choco’ is not recognized as an internal or external command,
operable program or batch file.

Is there a way to have the ‘execute command’ use the same environment (PATH, etc.) like if I would be logged in via the same user ‘locally’? Or do I have to always use the full paths to non-system tools/apps?

Thanks!

2

Hi,

If ALL your machines have this app installed with it present in it’s PATH and it’s the system PATH (not current user) and all machine have been restarted (or logged off and back on again), then a remote exec command should be working fine here, with no need for the full absolute path. ie: if it works locally on a slave node with the same user account, then it should work fine when done remotely using the same user account executed within.

Depending on your needs/for greater flexibility for the future as a general purpose pipeline tool, it might be nicer for you to implement a python script for “slave” with a UI to your suiting:
docs.thinkboxsoftware.com/produc … ve-scripts

3

ok, have to check about the restart. Haven’t done a restart yet, as the installation of chocolatey didn’t requested for one.