recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
a3d115d6e355fd0531dd99e3576bdfbc1aff4bac
cc-ci/machine-docs/JOURNAL-regall.md
autonomic-bot 4d54123d03
All checks were successful
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone Build is passing
Details
chore(regall): bootstrap phase state (STATUS/BACKLOG/REVIEW/JOURNAL-regall)
2026-06-17 01:56:27 +00:00

1.5 KiB
Raw Blame History

JOURNAL — phase regall

2026-06-17 — Phase bootstrap + sweep start

Context

Phase prevb completed with DONE at b6f526a. The prevb change introduced:

  • Dynamic upgrade-base resolution: last-green (warm canonical) → main-tip (ref) → skip
  • previous/ overlay mechanism (base-only, version-guarded)
  • Environmental vs version-specific overlay split

There are NO warm canonical registry records on the server (/var/lib/ci-warm/ has only keycloak/traefik reconciler dirs, no canonical.json). So for all recipes, the post-prevb base resolution will use main-tip ref as the upgrade base (kind=ref), unless:

  • EXPECTED_NA[upgrade] is declared (bluesky-pds → skip)
  • UPGRADE_BASE_VERSION is set (plausible → version 3.0.1+v2.0.0)

This is the key structural difference from pre-prevb: old code used lifecycle.previous_version(recipe) (the previous published tag), new code uses main-tip commit ref for most recipes.

Three prevb spot-checks already confirmed green with post-prevb code:

  • cryptpad PR#5: kind=ref main-tip 36ee3451; upgrade=pass
  • keycloak PR#3: kind=ref main-tip 12ac6db8; upgrade=pass (prune-orphans safe-skip)
  • hedgedoc PR#1: kind=ref main-tip 09bf4d54; upgrade=pass

Remaining 18 recipes to sweep.

Sweep strategy

  • Batch ≤3 concurrent Drone builds via !testme on open PRs
  • Create trivial "chore: regall test trigger" PRs for recipes with no open PRs
  • Monitor Drone build numbers, collect results.json levels
  • Compare to baseline table