Bug: host specific Deadline plugins crashing outside their context

[antirotor]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior:

Host specific deadline plugins are registered even outside their respective hosts. Because of their top-level imports of host API, they crash - silently because pyblish will just log crashing plugin but won't stop running.

Expected Behavior:

We should move host specific plugins to their respective folders and these folders only inside the host. That will clear up the log, speed discovery a little bit and also avoid a lot of confusion when debugging failed publishes.

As a next step, we should change the pyblish logic not to skip crashing plugin with some transition period.

Version

3.18.4-nightly.1

What platform you are running OpenPype on?

Windows

Steps To Reproduce:

Publish something in Nuke with Deadline addon enabled
You'll see some crashed plugins in Crashed Plugins log.

Are there any labels you wish to add?

• I have added the relevant labels to the bug report.

Relevant log output:

No response

Additional context:

No response

[cuID:OP-7976]

[BigRoy]

Most of these were resolved recently by moving the imports, but one import was missed for the maya plug-in (RenderSettings import).
However, I would really like it actually if the Deadline module would only install host specific plug-ins if it is inside that host. That would likely mean having a host specific subfolder in Deadline module plugins/publish like:

plugins/publish/maya
plugins/publish/houdini

Which then get registered maybe in the Addon in on_host_install. Thoughts?

If you agree - I can try and make this change quickly.