fix(ci): restore non110 cd push trigger
Some checks failed
CD Pipeline / workflow-shape (push) Successful in 1s
CD Pipeline / cancel-stale-cd (push) Has been skipped
CD Pipeline / tests (push) Failing after 23s
CD Pipeline / build-and-deploy (push) Has been skipped
CD Pipeline / post-deploy-checks (push) Has been skipped
Some checks failed
CD Pipeline / workflow-shape (push) Successful in 1s
CD Pipeline / cancel-stale-cd (push) Has been skipped
CD Pipeline / tests (push) Failing after 23s
CD Pipeline / build-and-deploy (push) Has been skipped
CD Pipeline / post-deploy-checks (push) Has been skipped
This commit is contained in:
@@ -10,12 +10,14 @@
|
||||
name: CD Pipeline
|
||||
|
||||
on:
|
||||
# 2026-06-28 Codex: 110 host runner/CD lane pressure incident.
|
||||
# Production CD remains workflow_dispatch only until a non-110 or hard-limited
|
||||
# runner passes readiness. Host pressure and Docker lock gates stay fail-hard
|
||||
# during the 110 capacity incident.
|
||||
# Push-triggered CD stays off until runner relocation or non-110 hard limits
|
||||
# satisfy ops/runner/guard-gitea-runner-pressure.py.
|
||||
# 2026-06-29 Codex: restore main push CD only after the non-110
|
||||
# awoooi-non110-* runner lane read back registration metadata, active
|
||||
# service, capacity=1, pressure OK, rollback unit, and label target-match.
|
||||
# 110 incident runner labels and generic labels remain fail-closed via
|
||||
# ops/runner/guard-gitea-runner-pressure.py.
|
||||
push:
|
||||
branches:
|
||||
- main
|
||||
workflow_dispatch:
|
||||
# 手動觸發永遠可用(用於補跑、緊急部署)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user