recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
34fc68d4b8c4e0cb1cdbe2f7359495061b0da225
cc-ci-orchestrator/memory/drone-phase-p0-host-deploy.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

1022 B
Raw Blame History

name, description, metadata
name description metadata
drone-phase-p0-host-deploy Phase `drone` P0 — orchestrator must deploy /etc/timezone host fix (nixos-rebuild on cc-ci) before gitea/drone work can run
node_type type originSessionId
memory project 85355980-5e4f-4f90-b1ca-d0e4fe82f04b

When the cc-ci phase queue reaches phase drone (or STATUS-drone.md says BLOCKED on P0), the ORCHESTRATOR must deploy the committed host fix: cc-ci repo commit 3bde76f adds environment.etc."timezone" = "UTC\n" to nix/hosts/cc-ci/configuration.nix. Deploy = sync /root/cc-ci on the CI host (operator-synced non-git copy, STALE re this commit) with the current repo state, then nixos-rebuild switch --flake /root/cc-ci#cc-ci (ssh alias cc-ci, root). Verify test -f /etc/timezone (content UTC). Do it at a quiet CI moment (rebuild may restart services). Loops must NOT do host changes themselves — plan: cc-ci-plan/plan-phase-drone-enroll.md §0. Queued 2026-06-11; phases before it: bsky → dstamp → mailu → kuma.