recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
a31095a087e82491dbed7a04c3aec0f18aa1dc8c
cc-ci/machine-docs/STATUS-1d.md

3.0 KiB
Raw Blame History

STATUS — Phase 1d (generic test suite + layered recipe overlays)

Phase plan (SSOT): /srv/cc-ci/cc-ci-plan/plan-phase1d-generic-test-suite.md Loop state for THIS phase: STATUS-1d / BACKLOG-1d / REVIEW-1d / JOURNAL-1d (DECISIONS.md shared). The repo's STATUS.md/BACKLOG.md/REVIEW.md (Phase 1) and STATUS-1b/1c (DONE) are HISTORY, not this phase's state.

Phase

Phase 1d runs after Phase 1b (DONE) and before Phase 2. It is the test-architecture foundation: every recipe gets a generic lifecycle suite for free; recipe-specific tests layer on top (override-or-extend). Bounded — build the architecture + prove it on a couple of recipes; full per-recipe overlay authoring is Phase 2.

Definition of Done (Phase 1d) — DG1–DG8, each Adversary cold-verified in REVIEW-1d

  • DG1 — Generic INSTALL test (recipe-agnostic): app new→deploy→converged→really serving (real HTTP(S), not Traefik fallback). Green on a simple recipe with no cc-ci/repo-local tests.
  • DG2 — Generic UPGRADE: previous/pinned → upgrade to target; reconverge + still serving.
  • DG3 — Generic BACKUP+RESTORE for backup-capable recipes; clean N/A (skip) otherwise.
  • DG4 — Layering (override-or-extend; generic is the default); discovery + cc-ci/repo-local precedence settled in DECISIONS. Invariant: no overlay for an op ⇒ generic runs.
  • DG4.1 — Overlays reuse the deployment: ONE deploy + ONE teardown per run; no extra new/deploy/undeploy (assert via deploy-count).
  • DG5 — Custom install-steps hook + graceful-generic rule; fail-without / pass-with proof.
  • DG6 — !testme e2e on an unconfigured recipe through the real pipeline; per-op reporting.
  • DG7 — Real, DRY, clean: no softened/skip/xfail assertions; generic in the shared harness; teardown always; respects MAX_TESTS.
  • DG8 — Documented (docs/ explains the generic suite, overlay convention, hook) + cold-verify.

Milestones (plan §3)

  • G0 — Generic install + deploy-once orchestrator; green on custom-html-tiny. Accept: DG1.
  • G1 — Generic upgrade + backup/restore. Accept: DG2, DG3.
  • G2 — Layering + discovery + precedence. Accept: DG4, DG4.1.
  • G3 — Custom install-steps hook + graceful-generic. Accept: DG5.
  • G4 — !testme e2e + per-op reporting + docs + cold verify. Accept: DG6, DG7, DG8 → DONE.

In flight

G0 — generic install + deploy-once orchestrator. Design recorded in DECISIONS.md (tier model, override precedence, deploy-once, backup-capability auto-detect, install-steps shell hook). Building harness/generic.py + harness/discovery.py + new deploy-once run_recipe_ci.py + tests/_generic/.

Gate

(none yet — will claim G0 when generic install is green on custom-html-tiny)

Blocked

(none) — bootstrap access re-verified @2026-05-27: ssh cc-ci ok (root, NixOS 24.11), abra 0.13.0-beta, 5 infra stacks up (traefik/drone/bridge/dashboard/backups), custom-html-tiny mirrored.