Houdini: Remove unused "remote publish" workflow for Houdini #693
+2
−205
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelog Description
Remove the "Remote Publish" workflow that lives within the
ayon_houdini
codebase but is unused. Some farm submissions for rendering and caching do work, with render targets allow local, farm rendering and using existing frames (for some) but none of these seem to rely on this Remote Publish logic that essentially was unused and likely would not work at all.Additional info
This likely was once a 'straight' copy from
colorbleed
codebase back in the Avalon-era.I also detected one other plug-in that seemed to have
deadline
as registered target for the Pyblish plug-in here (reported on discord). Which likely tells me that this plug-in is currently never triggering since we never seem to be registering that target. We only ever seem to registerlocal
,farm
,remote
andautomated
according to the codebase.Testing notes: