Deadline Plugin Environment needs to inherit Slave Environment... How?

Deadline
1

Im trying to figure out how all this plugin sandboxing concept works in deadline.

Apparently from version 8.0 there is this sandbox feature which if i understand correctly allows each deadline plugin to run in its own environment. This allows to prevent that the interaction between plugins messes with each other’s environment… okey.

My question is: if a slave machine has installed several renderers and each puts their own environment variables in the system… would those env vars be accessible from a deadline plugin running in sandbox mode?

How can i make a deadline plugin environment inherit the one of the slave machine and still keep it separate from another plugin’s environment?

In the “configure repository options” window i see those two options:

  • disable plugin sandboxing
  • run plugin sandbox in job’s environment

Have read the documentation and still not sure what those two options do.

2

Not sure if this is correct but from my understanding - each process will pick up all the system environment by default. They will only be overridden manually, with either job preload scripts or job’s environment on submission. In these cases the sand box will ensure that your custom variables are contained within that job’s process and never affect the OS level variable.
Reference:
JobPreload.py section in this link.
https://docs.thinkboxsoftware.com/products/deadline/8.0/1_User%20Manual/manual/application-plugins.html
And Job Environment
https://docs.thinkboxsoftware.com/products/deadline/8.0/1_User%20Manual/manual/environment.html

3

yess, that s my understanding as well.

Turns out we had set some system variables after the deadline launcher.exe was run, so the variables werent picked up. A simple restart and it worked.