We are creating a release version of our pipeline tools and loading this version via env variables. This is to intact older scenes and not have any issues. We have a few custom deadline plugins that recently had to have a major upgrade and not backwards compatible anymore.

Is there any env we can pass to deadline to load the custom folder from a different dir? Or something we can put into a job file to load the plugin from a folder location?

Or is the only way to name the custom deadline plugin with the version name in it? like:
myHoudiniPlugin_01
myHoudiniPlugin_02
myHoudiniPlugin_03

Cheers

There’s this guy:

docs.thinkboxsoftware.com/produ … ustom-path

You’ll have to reload the Deadline application in question (Slave, Monitor, etc) for it to take effect. It’s also the entire custom folder.

How granular do you need to be here? It may be possible to just use Python tricks to abstract which script gets loaded / called.