Skip to content
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.

General: Expose cleanup plugin settings #5141

Closed

Conversation

fabiaserra
Copy link
Contributor

Changelog Description

Expose the clean up plugins settings so they can be enabled/disabled.

This also exposes the optional key on all the clean up plugins so they could be optionally disabled during the publish. However, is the optional key having any effect in the new publisher?

Before
image

After
image

Testing notes:

  1. Open the Studio Settings and disable the Explicit Clean up plugin

@ynbot ynbot added host: Nuke size/XS Denotes a PR changes 0-99 lines, ignoring general files type: bug Something isn't working labels Jun 14, 2023
@fabiaserra fabiaserra requested a review from iLLiCiTiT June 14, 2023 18:25
Copy link
Contributor

@Minkiu Minkiu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haven't tested, but the code looks good.

@fabiaserra fabiaserra requested a review from iLLiCiTiT August 29, 2023 22:48
@Minkiu Minkiu assigned iLLiCiTiT and unassigned fabiaserra Sep 4, 2023
@ynbot ynbot removed the host: Nuke label Sep 4, 2023
@iLLiCiTiT
Copy link
Member

Open the Studio Settings and disable the Explicit Clean up plugin

I'm sorry, I'm looking at this PR, and I forgot what was the reason to have option to disable the plugin?

@fabiaserra
Copy link
Contributor Author

Open the Studio Settings and disable the Explicit Clean up plugin

I'm sorry, I'm looking at this PR, and I forgot what was the reason to have option to disable the plugin?

Because I didn't want any plugins to "explicitly" delete anything, I wanted to be the one that "explicitly" chose when I actually want things to be deleted so I wanted to have the option to disable the plugin

@fabiaserra
Copy link
Contributor Author

Open the Studio Settings and disable the Explicit Clean up plugin

I'm sorry, I'm looking at this PR, and I forgot what was the reason to have option to disable the plugin?

Because I didn't want any plugins to "explicitly" delete anything, I wanted to be the one that "explicitly" chose when I actually want things to be deleted so I wanted to have the option to disable the plugin

It's been that long though that I no longer know if it still has any impact on my fork but I do remember experiencing some files being deleted due to the Explicit Clean Up that I actually didn't want deleted

@iLLiCiTiT
Copy link
Member

It's been that long though that I no longer know if it still has any impact on my fork but I do remember experiencing some files being deleted due to the Explicit Clean Up that I actually didn't want deleted

Can you please revisit that? Because I know we had issues and they should be resolved now. I don't think it's good idea to have setting to disable this plugin.

@BigRoy
Copy link
Collaborator

BigRoy commented Sep 29, 2023

Does this PR allow me to disable the feature? that on a render publish from deadline that it DELETES the source render files? There've been quite a few times where one machine messed up in the render - the sequence got published; all source renders were deleted and we now have to re-render the full sequence instead of just 2 frames to publish it again. Drives us mad.

How can we disable the feature to remove the "render files" from the work/staging area - in our case referring to Maya + Fusion. Is there a setting for that somewhere?

@fabiaserra
Copy link
Contributor Author

Does this PR allow me to disable the feature? that on a render publish from deadline that it DELETES the source render files? There've been quite a few times where one machine messed up in the render - the sequence got published; all source renders were deleted and we now have to re-render the full sequence instead of just 2 frames to publish it again. Drives us mad.

How can we disable the feature to remove the "render files" from the work/staging area - in our case referring to Maya + Fusion. Is there a setting for that somewhere?

Right? I feel the same way, I want to have full control of when files get deleted as I've been in the same situation where in the farm the staging temporary files get deleted and it would have been very useful to be able to toggle that off so I can debug what happened or pick it up from those intermediate files

@fabiaserra
Copy link
Contributor Author

Does this PR allow me to disable the feature? that on a render publish from deadline that it DELETES the source render files? There've been quite a few times where one machine messed up in the render - the sequence got published; all source renders were deleted and we now have to re-render the full sequence instead of just 2 frames to publish it again. Drives us mad.
How can we disable the feature to remove the "render files" from the work/staging area - in our case referring to Maya + Fusion. Is there a setting for that somewhere?

Right? I feel the same way, I want to have full control of when files get deleted as I've been in the same situation where in the farm the staging temporary files get deleted and it would have been very useful to be able to toggle that off so I can debug what happened or pick it up from those intermediate files

I owe @iLLiCiTiT a test to confirm whether these changes actually have any effect

@mkolar
Copy link
Member

mkolar commented Feb 6, 2024

Boys, because we're splitting OpenPype into ayon-core and individual host addons, this PR would have to be re-created to target one of those. Also it probably needs to be properly re-validated :)

We're closing it down, but we'll he happy for a new PR to ynput/ayon-core repository once it's up.

@mkolar mkolar closed this Feb 6, 2024
@ynbot ynbot added this to the next-patch milestone Feb 6, 2024
@jakubjezek001 jakubjezek001 removed this from the next-patch milestone Feb 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
community contribution size/XS Denotes a PR changes 0-99 lines, ignoring general files type: bug Something isn't working
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

8 participants