status(2): discourse Q4.6 install+custom GREEN (re-pin + healthcheck overlay both work, pr5) — next: §4.3 create-topic + full lifecycle → claim
This commit is contained in:
@ -1064,3 +1064,13 @@ API HTTP 200, wildcard DNS resolves to gateway 143.244.213.108.
|
||||
`runner/run_recipe_ci.py::fetch_recipe`. Pre-existing in Phase 1d; not a 1e regression. Drone
|
||||
caps `MAX_TESTS=1` today, so practical impact bounded. Tracked for Phase-2 breadth-ramp if
|
||||
concurrent recipe runs become routine.
|
||||
|
||||
### discourse Q4.6 — UPDATE @2026-05-30: install+custom GREEN (re-pin + healthcheck overlay both work)
|
||||
`/root/ccci-discourse-pr5.log` (REF 7b7ddd70bc753608d086884b8de1ad3c327d9ac5, cc-ci HEAD 0e3049b):
|
||||
RUN SUMMARY deploy-count=1, **install:pass, custom:pass**. Both fixes proven: (1) bitnamilegacy
|
||||
re-pin (PR#1), (2) cc-ci healthcheck-overlay (compose.ccci-health.yml version:"3.8"+app
|
||||
start_period:1200s via install_steps + recipe_meta COMPOSE_FILE+CHAOS_BASE_DEPLOY+TIMEOUT/DEPLOY_TIMEOUT
|
||||
2400). Earlier failures were: 1800s timeout (slow Rails boot) → bumped timeout+start_period; then lint
|
||||
R011/R012 version-mismatch FATA → overlay needed matching version:"3.8". **NEXT:** author ≥2 discourse
|
||||
functional (incl §4.3 create-topic) for P3 — currently only health_check; then FULL lifecycle
|
||||
(install,upgrade,backup,restore,custom) green → CLAIM Q4.6. NOT yet claimed.
|
||||
|
||||
Reference in New Issue
Block a user