recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
03343ed3cfa0b94f8e0d5a00a4225b569cb270e2
cc-ci-orchestrator/memory/weekly-upgrade-queued-after-phases.md
autonomic-bot c33b21fe8d memory: commit session notes (drone P0, weekly-upgrade-queued, mailu/index updates) 
Per AGENTS.md 'Agent memory lives in memory/ (in this repo)' — memory notes
must be committed + pushed like any repo change, not left only in the local
~/.claude symlink target.
2026-06-11 20:56:24 +00:00

1.4 KiB
Raw Blame History

name, description, metadata
name description metadata
weekly-upgrade-queued-after-phases Weekly /upgrade-all cron skipped for 2026-06-12; queued to auto-run when the current phase queue finishes (drone)
node_type type originSessionId
memory project 85355980-5e4f-4f90-b1ca-d0e4fe82f04b

Operator (2026-06-11) cancelled tonight's weekly /upgrade-all cron run and queued it to run once after the current phase queue (…mailu→drone) completes instead.

  • cc-ci-upgrade-all.timer was STOPPED (couldn't disable — /etc/systemd is read-only). Its persistent stamp was forwarded to 2026-06-12 03:00 UTC so a reboot/nixos-rebuild tonight schedules the NEXT run for 06-19, not a catch-up of tonight's slot.
  • GOTCHA: systemctl start cc-ci-upgrade-all.timer fires the service IMMEDIATELY (Persistent=true). Do NOT start it to re-arm — let a host reboot/nixos-rebuild reactivate it (the drone-phase-p0-host-deploy rebuild will); the forward stamp prevents a catch-up fire.
  • Post-phase auto-run is wired in launch.py (commit 3fa3178): the watchdog launches launch-upgrader.py start when the LAST phase reaches ## DONE, gated by the one-shot flag /srv/cc-ci/.cc-ci-logs/.run-upgrade-on-complete (set 2026-06-11, consumed on fire). So when phase drone finishes, /upgrade-all starts automatically (upgrader on sonnet).

Once this fires (or if the plan changes), this memory is stale — delete it.