Commit Graph
3 Commits
Author SHA1 Message Date
Lucas Berger 667f01702c feat(08-02): ci.yml fast-checks job
- on: pull_request + push branches:[main]; workflow env MILESTONE: v1.1
- fast-checks job: runs-on ubuntu-latest, if pull_request
- Node 22 via actions/setup-node@v4 + corepack enable pnpm
- No actions/cache (D-PROBE-04: times out on this runner)
- pnpm install --frozen-lockfile, lint (no-op), typecheck, PWA unit tests
- DB-backed pnpm test intentionally absent from this job
2026-06-11 10:21:17 -04:00
Lucas Berger 134d4db08a fix(08-01): probe runs-on ubuntu-latest — runner has no self-hosted label
runner-probe / runner-probe (push) Successful in 5m33s
The act_runner advertises ubuntu-latest/ubuntu-24.04/ubuntu-22.04; runs-on:
self-hosted matched no runner and the probe job stayed queued. Switch the
probe (and the plan key-link) to ubuntu-latest. ci.yml (Plans 02-04) must
use the same label.
2026-06-11 10:04:41 -04:00
Lucas Berger b333d7b7ea feat(08-01): add runner-probe workflow
- Probe-only workflow triggering on gsd/phase-08-gitea-ci branch only
- Answers P-01..P-11 + P-13: Node version, pnpm, runner mode (critical
  fork Docker vs host), Docker socket, MariaDB service container spawn
  and reachability on both hostnames, actions/cache, Playwright WebKit
  deps, gitea-upload-artifact fork, and GITHUB_SHA short-SHA expression
- Uses healthcheck.sh --connect --innodb_initialized for MariaDB (never
  the binary removed from mariadb:11 — Pitfall 11)
- Uses ChristopherHX/gitea-upload-artifact@v4 (not the official action
  which aborts on Gitea with GHES detection — Pitfall 6 / T-08-SC)
- P-12 (docker login) deferred to Plan 04 — probe never references any
  secret (T-08-01 compliant)
- All steps that may fail use continue-on-error: true so probe reports
  findings instead of red-failing on expected unknowns
2026-06-11 09:53:13 -04:00