journal(prevb): all 5 discourse tiers green locally (custom mint_admin fixed); posting !testme for B7
This commit is contained in:
@ -107,3 +107,17 @@ M2 plan: B7 = discourse PR#4 !testme GREEN in real CI (Drone). Infra confirmed h
|
||||
(= my prevb code). Before posting !testme publicly on PR#4, running the FULL pipeline locally first
|
||||
(STAGES=install,upgrade,backup,restore,custom) to de-risk backup/restore/custom under the new model (my
|
||||
local runs so far were install,upgrade only). If a non-prevb tier fails I fix/triage first, then !testme.
|
||||
|
||||
## 2026-06-17T01:30Z — All 5 discourse tiers green locally; posting !testme (B7)
|
||||
|
||||
Full local run (run-prevb-disc-full) found ONE failure: custom `test_create_topic_roundtrip` — `mint_admin`
|
||||
hardcoded the bitnamilegacy path `/opt/bitnami/discourse` (404 on the official head). This is a DIRECT
|
||||
consequence of prevb working (the head is now genuinely official, not overlay-reverted to bitnamilegacy).
|
||||
Fixed `_discourse.py::mint_admin` image-agnostic (b66abc4): detect /var/www/discourse (official) vs
|
||||
/opt/bitnami/discourse (legacy); on official re-export DISCOURSE_DB_PASSWORD from /run/secrets/db_password
|
||||
(entrypoint exports it only for boot) and run bin/rails as root (official image USER is empty → exec=root;
|
||||
verified it works). Re-run (install,upgrade,custom) → custom PASS (all 3 custom tests green).
|
||||
|
||||
Tier status (across run-prevb-disc-full + run-prevb-disc-custom): install✓ upgrade✓ backup✓ restore✓ custom✓.
|
||||
So the real-CI !testme full pipeline should be green. Posting !testme on discourse PR#4 as autonomic-bot
|
||||
(authorized org member) → bridge (polls every 30s) triggers a Drone build of cc-ci@main (= prevb code).
|
||||
|
||||
Reference in New Issue
Block a user