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
a2c01f8: The fleet job service (A11-243): fleet work is a job you submit and follow by job ID, not a script in your own shell. a11y-fleet-jobs.service is a long-lived process on the control plane that owns a job store (/var/lib/a11y-fleet-jobs, files with one writer each) and runs each job's captures against the fleet over the workers' own /capture, so a job outlives the agent that submitted it. fleet capture submit takes the pages, the boxes (a number, ready or names), the capture options of the current scripts, a freeze reference and a label, and returns the job ID at once. fleet job status [--json] gives the state, progress per box, an estimated finish and the results' location; fleet job wait --timeout <duration> always ends (0 done, 1 failed with the reason, 3 cancelled, 124 timeout with the progress and what is left, 2 usage or unreachable); fleet job cancel, list --label and fetch complete it. Results are one record per page and pass plus a manifest.json (pages, boxes with their builds and versions, the pinned versions, start and finish) in a fixed place per job, copied to the agents host by fetch. Two jobs never share a box, a box that fails three captures in a row is dropped from its job, and a restart resumes every running job and takes again only the captures the dead process had sent. The CLI reaches the service over the control plane's ssh (a new controlPlaneInvocation beside sshToControlPlane), so there is no new port. It is put on the plane by pnpm run fleet:jobs-install, which runs the service from its own checkout, /root/fleet-jobs, and reads the heartbeat back. Nothing on any box changes; the fleet stays frozen.