M8/D7 gate CLAIMED: PR-comment outcome reflection verified; dashboard live
All checks were successful
continuous-integration/drone/push Build is passing
All checks were successful
continuous-integration/drone/push Build is passing
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
15
JOURNAL.md
15
JOURNAL.md
@ -656,3 +656,18 @@ NOTE: the bridge image has the same latent `:latest` issue (only rolled this ses
|
||||
Remaining M8 piece: PR-comment **outcome reflection** — the bridge posts the start/run-link comment
|
||||
but doesn't yet update it with the final pass/fail (needs a Drone build-completion hook or the
|
||||
bridge polling build status). Overview + badges (the core of D7) are done.
|
||||
|
||||
---
|
||||
## 2026-05-27 — M8/D7 complete: PR-comment outcome reflection + gate claim
|
||||
|
||||
Added outcome reflection to the bridge: after triggering, a daemon watcher polls the Drone build to
|
||||
completion and edits the run-link PR comment to ✅ passed / ❌ <status> (Gitea PATCH
|
||||
issues/comments/{id}). Gave the bridge image a content-hash tag so the swarm service actually rolls
|
||||
on bridge.py changes (same latent :latest no-roll issue the dashboard had).
|
||||
|
||||
Verified end-to-end: posted a fresh `!testme` on PR #1 → poller fired → "started" comment posted →
|
||||
build #76 (RECIPE=cc-ci, fails fast: no tests/cc-ci) → within ~20s the **same comment was edited to
|
||||
`cc-ci: run for cc-ci @ d397720a ❌ failure → …/76`**. The pass/fail now mirrors onto the PR comment.
|
||||
|
||||
D7 fully met: per-run logs (Drone UI) + overview page with badges (dashboard, live) + PR comment
|
||||
links back AND reflects the outcome. Claiming the M8 gate.
|
||||
|
||||
Reference in New Issue
Block a user