fix(cd): retry AI automation closure deploy
Some checks failed
Code Review / ai-code-review (push) Successful in 30s
CD Pipeline / tests (push) Successful in 1m47s
Ansible / Reboot Recovery Contract / validate (push) Has been cancelled
CD Pipeline / post-deploy-checks (push) Has been cancelled
CD Pipeline / build-and-deploy (push) Has been cancelled

This commit is contained in:
Your Name
2026-06-27 14:54:13 +08:00
parent 7abb824dc0
commit cea5d02363
2 changed files with 1 additions and 9 deletions

View File

@@ -312,11 +312,6 @@ jobs:
# 2026-04-30 Codex: Docker builds run on the host runner. Long docker build
# steps were killing the transient act job container with RWLayer=nil.
needs: tests
# 2026-06-27 Codex: Gitea 1.25 can leave dependent jobs as
# "Blocked by required conditions" after tests succeed when relying on the
# implicit success() condition. Make the dependency result explicit so the
# latest runtime fixes actually deploy while still failing closed on tests.
if: ${{ needs.tests.result == 'success' }}
timeout-minutes: 60
runs-on: awoooi-host
steps:
@@ -1223,9 +1218,6 @@ jobs:
post-deploy-checks:
needs: build-and-deploy
# Keep post-deploy tied to a real build/deploy success instead of the
# implicit condition that can be misreported as blocked in Gitea.
if: ${{ needs.build-and-deploy.result == 'success' }}
timeout-minutes: 30
# 2026-04-30 Codex: keep post-deploy on the host runner too. Playwright
# install-deps can also kill the act-managed job container with RWLayer=nil.

View File

@@ -1 +1 @@
# 2026-06-27 explicit Gitea needs-result deploy trigger for AI automation closure
# 2026-06-27 retry AI automation closure deploy without dependent-job override