-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Jobs: Support for job-hold-until/Hold-Job/Release-Job #15
Comments
Moving this to v1.3 milestone; Smith is working on the job-password stuff. |
6 tasks
michaelrsweet
changed the title
Jobs: Support for job-hold-until/Hold-Job/Release-Job and job-password
Jobs: Support for job-hold-until/Hold-Job/Release-Job
Oct 24, 2022
job-password stuff is now being tracked separately in issue #225. |
michaelrsweet
added a commit
that referenced
this issue
Oct 25, 2022
Tracking development on the "job-hold-until" branch... |
michaelrsweet
added a commit
that referenced
this issue
Oct 27, 2022
- Check for more jobs to process after releasing. - When the output device is 'file:', always close when finishing the job. - Don't start processing a job if job-hold-until-specified is set. - Allow any job-hold-until value as long as it is one name or keyword. - Fix name of release web page. - Implement and hook up hold and release job web pages.
michaelrsweet
added a commit
that referenced
this issue
Oct 29, 2022
- Fix "busy" behavior for raster jobs. - Look for state transitions. - Look for output files at the wrong times. - Count the number of expected output files. - Check for jobs to process after Release-Held-New-Jobs.
michaelrsweet
added a commit
that referenced
this issue
Oct 30, 2022
- Add hold-new-jobs and release-held-new-jobs actions to printer page. - Refactor cancel, hold, release, and reprint job to go through the jobs page, like the printer operations go through the printer page.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Would be nice to support held jobs. Tasks:
The text was updated successfully, but these errors were encountered: