recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
85a781368a07545fffff8f909442601f0f32317f
cc-ci/machine-docs/STATUS-mailu.md
autonomic-bot 85a781368a
Some checks failed
continuous-integration/drone/push Build is failing
Details
machine-docs: move all per-phase coordination files out of repo root 
STATUS/BACKLOG/REVIEW/JOURNAL for bsky/conc/dstamp/kuma/lvl5/mailu/rcust/shot
(32 files) were at the repo root; move them into machine-docs/ to match the
mandated file-location rule (DECISIONS/DEFERRED/INBOX + older phases already
live there). AGENTS.md gains an explicit File-location rule. No content change.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-11 20:57:03 +00:00

4.2 KiB
Raw Blame History

STATUS — phase mailu (backupbot labels for mailu recipe)

Phase plan: /srv/cc-ci/cc-ci-plan/plan-phase-mailu-backup.md Builder: autonomic-bot / Claude (Builder loop) Started: 2026-06-11T18:00Z

Current state

Gate M1: CLAIMED — awaiting Adversary

Drone build #473: LEVEL 5 PASS at PR#3 head (edc0201a79d3), all rungs green including backup/restore on real seeded mail data. Claimed 2026-06-11T20:52Z.

Gate M2: NOT YET CLAIMED

DoD tracker (M1)

  • Data-layout research documented (which volumes hold durable state, justification in PR desc)
  • Recipe-mirror PR open with backupbot v2 labels (admin /data + imap /mail)
    • PR#3: recipe-maintainers/mailu#3
    • Branch: add-backupbot-labels, head commit: edc0201a79d36bc87696b0f93f1ee88ad7bd10ed
    • Version bump: 3.0.1+2024.06.52 → 3.0.2+2024.06.52
    • Adds deploy.labels: {backupbot.backup: "true", backupbot.backup.path: "/data"} to admin
    • Adds deploy.labels: {backupbot.backup: "true", backupbot.backup.path: "/mail"} to imap
  • Version label bumped in compose.yml (3.0.1 → 3.0.2+2024.06.52)
  • cc-ci: tests/mailu/ops.py with pre_backup (seed mailbox) + pre_restore (delete mailbox)
  • cc-ci: tests/mailu/test_backup.py asserting mailbox present at backup time
  • cc-ci: tests/mailu/test_restore.py asserting mailbox restored after restore
  • cc-ci: tests/mailu/PARITY.md updated (P4 now covered, not N/A)
  • Full lifecycle green at PR head (L5) including backup/restore rung — via drone !testme
    • Drone build #473: LEVEL 5 of 5 — all rungs PASS (install/upgrade/backup/restore/custom)
    • test_backup_captures_mailbox PASS — citest@<domain> present in config-export at backup time
    • test_restore_returns_mailbox PASS — citest@<domain> restored after pre_restore deletion
    • Backup snapshot: 13eee64e (139 files, 88MB, admin /data + imap /mail)
    • Clean teardown: no mailu-* stack left on host (docker stack ls confirms)
  • Before/after level recorded
    • BEFORE (main, no labels): backup_capable=False → backup rung = intentional-skip → max L4
    • AFTER (PR#3 head edc0201a): backup_capable=True (auto-detected from labels) → backup rung = PASS → L5

DoD tracker (M2)

  • Fresh Adversary cold pass (independent re-trigger at PR#3 head)
  • Levels reconciled
  • DEFERRED entry closed
  • STATUS-mailu.md operator summary
  • REVIEW-mailu.md shows PASS for M1 + M2 (within 24h)

Verification recipe (for Adversary M1 check)

# 1. Verify backupbot v2 labels in PR#3 compose.yml (branch: add-backupbot-labels)
GITEA_PASSWORD=$(grep GITEA_PASSWORD /srv/cc-ci/.testenv | cut -d= -f2-)
curl -s "https://git.autonomic.zone/api/v1/repos/recipe-maintainers/mailu/contents/compose.yml?ref=add-backupbot-labels" \
  -u "autonomic-bot:${GITEA_PASSWORD}" \
  | python3 -c "import sys,json,base64; print(base64.b64decode(json.load(sys.stdin)['content']).decode())" \
  | grep -A4 backupbot
# Expected:
#   admin service → backupbot.backup: "true" + backupbot.backup.path: "/data"
#   imap service  → backupbot.backup: "true" + backupbot.backup.path: "/mail"

# 2. Verify PR#3 head commit
# Expected: edc0201a79d36bc87696b0f93f1ee88ad7bd10ed

# 3. Verify drone build #473 level 5
DRONE_TOKEN=$(ssh cc-ci 'cat /run/secrets/bridge_drone_token')
curl -s "https://drone.ci.commoninternet.net/api/repos/recipe-maintainers/cc-ci/builds/473" \
  -H "Authorization: Bearer ${DRONE_TOKEN}" | python3 -c "
import sys,json; b=json.load(sys.stdin)
print('status:', b['status'])
print('steps:', [(s['name'], s['status']) for st in b['stages'] for s in st['steps']])
"
# Expected: success, clone+ci both success

# 4. Verify full results.json
ssh cc-ci 'cat /var/lib/cc-ci-runs/473/results.json'
# Expected: level=5, all rungs pass (backup_restore, functional, install, lint, upgrade)

# 5. Re-trigger to verify at current PR head (M2 requirement):
# Comment !testme on PR#3 as the Adversary and observe level 5 again

# 6. Confirm DEFERRED entry for mailu backup is closed (see machine-docs/DEFERRED.md)

Blocked items

(none)

DONE

Not yet. Written here only when all DoD items have M1+M2 Adversary PASS in REVIEW-mailu.md.