Environment variables in Deadline are not path mapped. I’m not sure if this is actually something which others would expect as a default behaviour as it is normal for env vars to be platform specific. However, if this is desired behaviour, you should be able to intercept the env var and path map using something like a JobPreLoad.py script which executes in front of the app plugin script. You could execute this for ALL jobs (any app plugins) if you use a GlobalJobPreLoad.py script. The reason you will probably need to do it ahead of the actual Python.py ap plugin script firing is becauese whatever you are executing within the Python.py plugin might need to ‘see’ these env vars earlier in the process.
Here’s an example:
docs.thinkboxsoftware.com/produc … preload-py
The all important Scripting API function is:
docs.thinkboxsoftware.com/produc … 24500131a4
[code]import os
from Deadline.Scripting import *
def main( deadlinePlugin ):
incomingEnvVar = os.environ[“MY_ENV_VAR”]
convertedEnvVar = RepositoryUtils.CheckPathMapping( incomingEnvVar )
deadlinePlugin.SetProcessEnvironmentVariable( “MY_ENV_VAR”, convertedEnvVar )[/code]
If you are already including the env var within the submitted job in Deadline (instead of it being on the system already), then retrieve this env var using the job properties:
def __main__( deadlinePlugin ):
job = deadlinePlugin.GetJob()
job.GetJobEnvironmentKeyValue( "MY_ENV_VAR" )
Note: I didn’t test this code, but it should get you close…