fix(cd): clear empty docker build locks
All checks were successful
Code Review / ai-code-review (push) Successful in 10s
All checks were successful
Code Review / ai-code-review (push) Successful in 10s
This commit is contained in:
@@ -31,6 +31,14 @@
|
||||
**驗證**:
|
||||
- `kubectl kustomize k8s/awoooi-prod` 通過,build output 中 `drift-scanner` image 會被解析為目前 kustomization 的 `awoooi/api:c4854bb3...`。
|
||||
|
||||
## 2026-05-05 | CD Docker build 空鎖自動清理
|
||||
|
||||
**背景**:重開機後 Gitea Actions 曾留下 `awoooi-cd-docker-build-lock` Docker network 空鎖;live host 無 `docker build/buildx/docker push` 進程,但後續 CD 仍會等滿 30 分鐘才 timeout。
|
||||
|
||||
**本次修補**:
|
||||
- `.gitea/workflows/cd.yaml` 的 `Acquire Docker Build Lock` 新增 `EMPTY_LOCK_SECONDS=300`。
|
||||
- lock 超過 5 分鐘且 host 上沒有 active docker build/push 時,自動移除空鎖後重新嘗試取得 lock;真正超過 2 小時的 stale lock 仍保留原有強制清理邏輯。
|
||||
|
||||
## 2026-05-05 | 重開機後排程與 startup baseline 修復
|
||||
|
||||
**背景**:四台主機非預期重開機後,統帥要求確認所有服務、網站、工具、資料庫與排程都能正常恢復,不能只看容器 `healthy`。
|
||||
|
||||
Reference in New Issue
Block a user