Skip to content

v0.21.0

Choose a tag to compare

@github-actions github-actions released this 25 Oct 18:32
· 24 commits to main since this release

Minor Changes

  • e1d40ca: The lab reaches the fleet job service, and the lab catalogue hands its capture jobs a label and boxes (A11-263, step 2 of 4). ansible/fleet-jobs-lab-access.yml makes /root/.ssh/a11y-fleet-jobs on the lab (never copied off it), puts its public half in the control plane's authorized_keys as restrict,command="… src/fleet-jobs/gate.ts", checks control out on the lab at /opt/a11y-fleet-cli, writes /etc/a11ign/fleet.env and /usr/local/bin/fleet, and reads back from the lab that fleet lease list --json answers and that id over the key is refused. src/fleet-jobs/gate.ts runs remote.ts only in the form controlPlaneTransport sends (single-quoted arguments, no shell) and refuses every other command with exit 2; ADR 0004 gives the reasons. In lab-job.yml, label is a new published parameter, REQUIRED by every job that captures (capture, capture-only, both capture-acceptance, capture-real-pages, retrain, everything, evidence-check, stability, gate-stability, gate-probe-order, capture-check): a launch without it (or with one that is not a ticket key) is refused naming the parameter, by lab:job before any box is woken and by the playbook. Those jobs also set A11Y_FLEET_BOXES (the workers or worker name or count, else ready), A11Y_FLEET_LABEL and A11Y_FLEET_WAIT (the job's own timeout); a lab older than step 3 never reads them. lab:pipeline takes --label=<ticket key> and passes it to the stages that take one (a pipeline that captures is refused without it, before its unit starts), and a --qualify-sha run that names no label is booked as qualify-<row>. Revert: remove the three variables and the label parameter from the catalogue, the --label flag from lab-pipeline.ts, the default label from qualification-run.ts, and gate.ts with its play; remove the a11y-lab-fleet-jobs line from root's authorized_keys on the control plane.