-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added possibility to control state of Publish job in Settings and Publisher UI #131
base: develop
Are you sure you want to change the base?
Added possibility to control state of Publish job in Settings and Publisher UI #131
Conversation
Should be collected in CollectJobInfo to track state of publish job.
server/settings/publish_plugins.py
Outdated
@@ -40,6 +40,7 @@ def extract_jobinfo_overrides_enum(): | |||
{"value": "secondary_pool", "label": "Secondary pool"}, | |||
{"value": "machine_list", "label": "Machine List"}, | |||
{"value": "machine_list_deny", "label": "Machine List is a Deny"}, | |||
{"value": "publish_job_suspended", "label": "Publish Job Suspended"}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that "action" name is easier to understand.
{"value": "publish_job_suspended", "label": "Publish Job Suspended"}, | |
{"value": "suspend_publish_job", "label": "Suspend Publish Job"}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually think an enum is better: seeing it then be either Queued or Suspended then it's immediately clear what happens if you do not suspend it.
Plus it'd potentially allow different states.. if there are any that make sense
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So publish_job_state
instead?
Changelog Description
Publish job could be set as
Suspended
to allow artist publish only after some necessary checks are made. This was previously possible only in Publisher UI, but even that was removed during refactoring.Now state of Publish job could be controlled by
Collect Job Info
configuration with Profiles and could be overridden by artist in Publisher UI if necessary.Testing notes:
ayon+settings://deadline/publish/CollectJobInfo/profiles/1/publish_job_suspended