NOTE: The MayaAdaptor expects that the MayaPY executable is named mayapy and is set on the PATH. If this is not the case, you can set the MAYA_ADAPTOR_MAYAPY_EXECUTABLE environment variable to the path to the MayaPy executable.
What was the problem/requirement? (What/Why)
If mayapy isn't in the default PATH, mayapy cannot be found
What was the solution? (How)
We have implemented an environment variable solution like was done for deadline-cloud-for-nuke.
What is the impact of this change?
Additional feature support for a new MAYA_ADAPTOR_MAYAPY_EXECUTABLE environment variable to point to a specific mayapy path.
How was this change tested?
Did you run the "Job Bundle Output Tests"? If not, why not? If so, paste the test results here.
Required: paste the contents of job_bundle_output_tests/test-job-bundle-results.txt here
Was this change documented?
Is this a breaking change?
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
NOTE: The MayaAdaptor expects that the MayaPY executable is named
mayapy
and is set on the PATH. If this is not the case, you can set theMAYA_ADAPTOR_MAYAPY_EXECUTABLE
environment variable to the path to the MayaPy executable.What was the problem/requirement? (What/Why)
If
mayapy
isn't in the default PATH, mayapy cannot be foundWhat was the solution? (How)
We have implemented an environment variable solution like was done for deadline-cloud-for-nuke.
What is the impact of this change?
Additional feature support for a new
MAYA_ADAPTOR_MAYAPY_EXECUTABLE
environment variable to point to a specific mayapy path.How was this change tested?
Did you run the "Job Bundle Output Tests"? If not, why not? If so, paste the test results here.
Was this change documented?
Is this a breaking change?
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.