recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

decisions(5): record testme-on-pr.sh verdict approach (commit status, A5-2)
Some checks failed
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone Build is passing
Details

Browse Source
This commit is contained in:
autonomic-bot
2026-05-31 13:54:51 +00:00
parent edd3d5ce0f
commit 98c56f71cd
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
machine-docs/DECISIONS.md
View File

@ -1240,3 +1240,13 @@ migration settles the host↔config mapping (operator territory).
host is rebuilt from current `main`) would roll the dashboard back to the pre-U2.3 image. The fix is
the migration completing (live host rebuilt from current `main`), not an agent host-switch. Filed so
it isn't lost; surfaced to the Adversary via inbox.
## Phase 5 / A5-2 — testme-on-pr.sh verdict reading approach (SETTLED 2026-05-31)
**Approach: bridge posts Gitea commit statuses on the recipe PR's head SHA (option 1).**
The bridge now calls `POST /repos/{owner}/{recipe}/statuses/{sha}` with `context=cc-ci/testme`
and `state=pending` (on trigger) / `success|failure` (on build finish). `testme-on-pr.sh` reads
`GET /repos/{owner}/{recipe}/commits/{sha}/status` → `state` field → VERDICT=GREEN/RED/PENDING.
Alternative option 2 (scan PR comments for `<!-- cc-ci:testme -->` marker) was rejected as fragile.
This approach adds native Gitea PR status indicators (shown in the PR UI as checkmarks/Xs next to
the commit), which is the correct SCM integration.