Support archiving jobs #99402

Open
opened 2022-07-04 14:55:05 +02:00 by Sybren A. Stüvel · 2 comments

Archiving jobs should be possible from the web interface.

Something like this might work:

  • Store the job & task database entries as JSON in one or more files in next to the task logs & last-rendered images.
  • Store the Shaman checkout definition there as well. This probably means that this should be stored at job creation, not entirely trivial.
  • ZIP everything together.
  • Move the ZIP to some archive location
  • Delete the job (see #99401).
Archiving jobs should be possible from the web interface. Something like this might work: - Store the job & task database entries as JSON in one or more files in next to the task logs & last-rendered images. - Store the Shaman checkout definition there as well. This probably means that this should be stored at job creation, not entirely trivial. - ZIP everything together. - Move the ZIP to some archive location - Delete the job (see #99401).
Author
Owner

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Owner

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren
Sybren A. Stüvel added
Type
Design
and removed
Type
Report
labels 2023-02-17 11:17:22 +01:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: studio/flamenco#99402
No description provided.