ci: drop the nightly-windev schedule; run the deep windev tier on demand
ci / portable (push) Failing after 10m10s
ci / java (push) Failing after 20m12s
ci / windows-x86 (push) Failing after 22m40s

The scheduled nightly-windev job failed most nights for host reasons and
filed a Gitea issue each time. Remove the cron trigger and the job, and add
a workflow_dispatch trigger whose windev_mode input (test/build/live) drives
the windows-x86 job, so the live tier runs on demand - from the Actions page
or via scripts/ci/run-windev-ci.sh live - the same way clients are packed and
published on demand. Docs updated to match.

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
Joseph Doherty
2026-11-15 09:42:13 -05:00
parent 26a90883fa
commit e74918ccfb
7 changed files with 65 additions and 85 deletions
+2 -1
View File
@@ -228,7 +228,8 @@ days. The SQLite DB must also never be opened with a host-side `sqlite3` while t
## 3. Preflight (no changes yet)
1. Decide the target SHA on `origin/main`; confirm CI is green for it (`windows-x86` job runs the
Worker build + `Worker.Tests` on windev; `nightly-windev` runs the live tier,
Worker build + `Worker.Tests` on windev; run the live tier on demand with
`CI_SHA=<sha> scripts/ci/run-windev-ci.sh live` or a `windev_mode: live` dispatch,
`scripts/ci/README.md`).
2. Read the current state of the service (read-only):
```text