Files
cc-ci/machine-docs/BACKLOG-dash.md
autonomic-bot f68f1c56d9
Some checks failed
continuous-integration/drone/push Build is failing
status(dash): ## DONE — M1+M2 fresh Adversary PASS (3595e80, 4c0b289), no VETO
Per-recipe history now sources the full run list from local /var/lib/cc-ci-runs
artifacts; deployed (image 11ac2a1e6c07, 1/1) + verified live: bluesky-pds 8 in
exact host ts order, ghost 24/immich 28/discourse 25, plausible/custom-html
capped 30 newest; overview+badges 200; traversal/injection rejected; retention
no-trim. DoD plan §5 met.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-17 16:40:29 +00:00

1.3 KiB

BACKLOG — phase dash

Build backlog

  • Root-cause confirmed (Drone 100-build window) + host artifact schema inspected.
  • M1: rewrite history_for to source from /var/lib/cc-ci-runs local artifacts, newest-first by finished, capped at HISTORY_CAP, malformed/empty dirs skipped, security/other routes unchanged.
  • M1: unit test for local sourcing (count/order/cap/skip) + full-fixture verify vs real data.
  • M1: awaiting Adversary PASS in REVIEW-dash.md.
  • M2: deployed. Procedure (host flake source = /etc/cc-ci git clone): ssh cc-ci 'git -C /etc/cc-ci pull && systemd-run --no-block --unit=ccci-dash-sw --collect --property=Type=oneshot nixos-rebuild switch --flake /etc/cc-ci#cc-ci'. Content-hash image tag rolls dashboard.py change: current deployed 15addbc7bf45 → expected new 11ac2a1e6c07 (sha256sum dashboard/dashboard.py | cut -c1-12). Then verify live on /recipe/bluesky-pds (8 runs) + ≥2 recipes, overview + badges still 200, deploy-dashboard active, host health after.
  • M2: retention confirmed — no trim job; does not trim /var/lib/cc-ci-runs (record in DECISIONS if a cap needed).
  • DONE: both gates Adversary-PASS in REVIEW-dash.md → write ## DONE in STATUS-dash.md.