You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
60f729c: The fleet job service takes jobs of cases, for lab's captures (A11-263, step 1 of 4). fleet capture submit --cases <file> submits a job whose every capture has its own id, URL and /capture body, sent exactly (the page job's defaults are not merged in), and an optional group: every case of a group is captured on one box, one after another and in file order, and a group is never split, even after a restart (a group moves only whole and only while untouched). A group may carry skipWhen, which skips it, with nothing sent and no record written, when the box's /health environment matches the named fields. fleet job recapture <id> --cases a,b --label <key> prints a new job ID for named cases of a done case job; each case is pinned to the box its group was captured on, the job asks for those boxes by name so it queues and leases like any named job (A11-244), and its records are <case>.a<attempt>.json. A job of cases or a re-capture is store version 2 (the service reads 1 and 2; a page job is still version 1, and an older service fails a case job by name). The manifest of a case job gains cases, recaptureOf, each capture's case, group and attempt, and each box's whole environment. A job of pages behaves as before. Revert: remove --cases and recapture from cli.ts and remote.ts; a page job reads and runs as it did.