Skip to content
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

Open
wants to merge 6 commits into
base: develop
Choose a base branch
from

Conversation

kalisp
Copy link
Member

@kalisp kalisp commented Feb 14, 2025

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:

  1. experiment with ayon+settings://deadline/publish/CollectJobInfo/profiles/1/publish_job_suspended
  2. check that values propagate to Publisher UI in DCC, try to change it
  3. publish in Deadline and check state of published job in DL Monitor

@kalisp kalisp added type: bug Something isn't working sponsored This is directly sponsored by a client or community member labels Feb 14, 2025
@kalisp kalisp self-assigned this Feb 14, 2025
@@ -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"},
Copy link
Member

@iLLiCiTiT iLLiCiTiT Feb 14, 2025

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.

Suggested change
{"value": "publish_job_suspended", "label": "Publish Job Suspended"},
{"value": "suspend_publish_job", "label": "Suspend Publish Job"},

Copy link
Contributor

@BigRoy BigRoy Feb 14, 2025

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

Copy link
Member

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sponsored This is directly sponsored by a client or community member type: bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants