In testing, test Jobs are being submitted with CustomPluginDirectory=X:/path/to/custom/plugins (not the actual path, but you get the idea), and at this location there are customized MayaBatch.py and JobPreLoad.py files. The Jobs are also submitted with Plugin=MayaBatch.
When these Jobs run, they seem to completely ignore CustomPluginDirectory, instead I see this in the logs (again, actual paths redacted):
…with no errors about being unable to find the CustomPluginDirectory path provided, and no indication it ever tried to look there. Instead, Deadline is using its defaults. In any case, the custom path provided should be accessible to Deadline.
Anyone have any clues as to why CustomPluginDirectory is being ignored when the Job runs?
When you created your custom plugin, did you also create a custom submission script? I think that’s prob. the part that is missing from your custom plugin setup.
I’m submitting MayaBatch Jobs via python code independent of the Monitor, the CustomPluginDirectory I specify is correctly getting set in those Job properties (one of the ways I can verify is via the Monitor Job Properties > Environment > Custom Plugin Directory), and the Jobs are running. The only unexpected thing is that when they run, they’re ignoring the CustomPluginDirectory path when they source JobPreload.py and MayaBatch.py, with no indication as to why.
Could you explain why it is that you think creating Monitor submission scripts specifically would solve this issue?
Just to follow up, this ended up being a simple mistake on my part, in that I didn’t have a MayaBatch folder under my CustomPluginDirectory path (e.g. the MayaBatch.py etc. files were directly in the X:/path/to/custom/plugins path). I’m assuming there were no errors thrown because the CustomPluginDirectory existed, it just didn’t contain the subfolder, so it resorted to the default location.
Added the missing subfolder & added the files to it, and now it’s working as expected without any other changes.