No automated way to set up a dev installer similar to the submitter installer
What was the solution? (How)
make a hatch run install command similar to houdini's (a lot of it was taken wholesale, like the _project file and bits of the install dev submitter file)
What is the impact of this change?
Users can now run
hatch run install
hatch shell
# launch maya, here's macos
open /Applications/Autodesk/maya2023/Maya.app
and then load it in the plugin window. Organization matches the install_builder component
It's definitely not the most perfected workflow, but it's an easy way to set-up the submitter that could then be used as the starting point for an installation script that lives outside of install builder.
How was this change tested?
Did it myself! I then loaded the submitter and confirmed that it used the development one
Did you run the "Job Bundle Output Tests"? If not, why not? If so, paste the test results here.
What was the problem/requirement? (What/Why)
No automated way to set up a dev installer similar to the submitter installer
What was the solution? (How)
make a
hatch run installcommand similar to houdini's (a lot of it was taken wholesale, like the _project file and bits of the install dev submitter file)What is the impact of this change?
Users can now run
and then load it in the plugin window. Organization matches the install_builder component
It's definitely not the most perfected workflow, but it's an easy way to set-up the submitter that could then be used as the starting point for an installation script that lives outside of install builder.
How was this change tested?
Did it myself! I then loaded the submitter and confirmed that it used the development one
Did you run the "Job Bundle Output Tests"? If not, why not? If so, paste the test results here.
N/A
Was this change documented?
Added to README
Is this a breaking change?
N/A