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
+13 -8
View File
@@ -26,10 +26,17 @@ Runs of SHAs older than that change still use the old directory lock and do not
runs; that window closes as branches rebase. each native command is checked
immediately and the first nonzero exit aborts the remaining tiers and propagates to CI.
CI jobs (`.gitea/workflows/ci.yml`): `windows-x86` runs `test` per push/PR (not on the schedule,
where it would duplicate the nightly's first two tiers and start a second windev session in the
same second); `nightly-windev` runs `live` on the `0 6 * * *` schedule and opens a Gitea issue on
failure.
CI jobs (`.gitea/workflows/ci.yml`): `windows-x86` runs `test` per push/PR. There is no
scheduled run. Run the `live` tier on demand, like the client pack/publish scripts:
```bash
# from a machine with SSH access to windev (falls back to the default SSH identity)
WINDEV_SSH_USER=<user> CI_SHA=$(git rev-parse HEAD) scripts/ci/run-windev-ci.sh live
```
or dispatch the `ci` workflow from the Gitea Actions page with `windev_mode: live`. The
`nightly-windev` cron job that used to run `live` every night and file a Gitea issue on failure
was removed on 2026-11-15: it failed most nights for host reasons and the issues were noise.
## One-time bring-up (operator — required before this lands on `main`)
@@ -53,8 +60,6 @@ first, then merge.
4. **Network precheck** — confirm the Gitea runner container (on the `traefik` docker network,
host `10.100.0.35`) can reach `10.100.0.48:22`: a one-off `nc -z -w5 10.100.0.48 22` step.
The network was created for gitea name resolution, not LAN egress, so verify.
5. **Actions token** — the `nightly-windev` on-failure step creates a Gitea issue with the
built-in token; confirm Actions tokens have issue-write on this repo.
## Verifying it end-to-end (design's acceptance checks)
@@ -63,8 +68,8 @@ first, then merge.
red; revert. (Proves exit-code propagation — the whole point.)
- Unreachable-host red: point at a bogus port / stop sshd, confirm the job fails fast, not hangs.
- Concurrency: push two branches back-to-back, confirm the second remote run waits on the lock.
- Nightly: trigger the schedule path, confirm `live` runs and a forced failure opens an issue.
**Done 2026-08-10** (Check 6). Verified two ways: (a) production — every red nightly since
- Nightly (historical — the job was removed 2026-11-15): trigger the schedule path, confirm
`live` runs and a forced failure opens an issue. **Done 2026-08-10** (Check 6). Verified two ways: (a) production — every red nightly since
2026-07-17 has auto-filed an issue (#126–#139) authored by the `gitea-actions` bot, e.g. run 672
→ issue #139, with the built-in token masked to `***` in the job log; (b) a forced-failure probe
on the throwaway branch `test/tst25-check6-nightly-issue` (run 677 → issue #140, since closed and