wooo/awoooi
1
1
Fork 0
Code Issues 2 Pull Requests 1 Actions 3 Packages Projects Releases Wiki Activity

fix(runner): classify blocked visible cd runs
Some checks failed
CD Pipeline / workflow-shape (push) Successful in 0s
Details
CD Pipeline / cancel-stale-cd (push) Has been skipped
Details
CD Pipeline / tests (push) Successful in 1m14s
Details
CD Pipeline / build-and-deploy (push) Failing after 2m34s
Details
CD Pipeline / post-deploy-checks (push) Has been skipped
Details

Browse Source
This commit is contained in:
Your Name
2026-06-30 20:27:52 +08:00
parent 2f40ebd0c9
commit b83a15136f
3 changed files with 39 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/LOGBOOK.md
View File

@@ -3,6 +3,7 @@
**照主線修正的問題**：
- `ops/runner/read-public-gitea-actions-queue.py` 新增 Harbor CD self-heal readback 欄位：`latest_visible_cd_harbor_controlled_repair_attempted`、`latest_visible_cd_harbor_controlled_repair_skip_reason`、`latest_visible_cd_harbor_controlled_repair_public_registry_v2_status`。
- Rollups 同步暴露 `current_main_cd_harbor_controlled_repair_attempted` 與 skip reason，讓 mainline dashboard 能分辨「registry `/v2/` 壞」與「CD self-heal 因非 110 runner / watchdog missing / disabled 而無法執行」。
- 新增 visible `Blocked` classifier：當 Gitea HTML 最新 CD run 顯示 Blocked，即使 jobs API 回 stale success，也回 `blocked_latest_visible_cd_run`，避免 stale jobs API 蓋掉 source truth。
- Regression fixture 新增 `harbor_controlled_repair_skipped=not_110_host`，鎖住目前 `#4053` 類型的失敗不會被泛化成單純 Harbor 502。
**驗證**：