ops/devops: add console offline runner spec and CI skeleton

This commit is contained in:
StellaOps Bot
2025-12-07 11:38:46 +00:00
parent e53a282fbe
commit af30fc322f
4 changed files with 69 additions and 72 deletions

View File

@@ -0,0 +1,29 @@
# Console CI runner (offline-friendly)
Status: baseline runner spec + CI skeleton; use to unblock DEVOPS-CONSOLE-23-001. Workloads remain manual-trigger until console team confirms budgets.
## Runner profile
- OS: Ubuntu 22.04 LTS (x86_64) with Docker available for Playwright deps if needed.
- Node: 20.x (LTS). Enable corepack; prefer npm (default) to avoid extra downloads.
- Caches:
- npm: `~/.npm` keyed by `src/Web/package-lock.json` hash.
- Playwright: `~/.cache/ms-playwright` pre-seeded with Chromium so `npm test -- --browsers=ChromeHeadless` can run offline. Seed once using `npx playwright install chromium` on a connected runner, then snapshot the directory into the runner image.
- Angular build cache: optional `~/.cache/angular` if using angular.json cache; safe to keep.
- Artifacts retention: keep lint/test/build outputs 14 days; limit to 500 MB per run (coverage + dist + test reports). Artifacts path: `artifacts/` (dist, coverage, junit/trx if produced).
## Pipeline steps (expected)
1) Checkout
2) Node 20 setup with npm cache restore (package-lock at `src/Web/package-lock.json`).
3) Install: `npm ci --prefer-offline --no-audit --progress=false` in `src/Web`.
4) Lint: `npm run lint -- --no-progress`.
5) Unit: `npm test -- --watch=false --browsers=ChromeHeadless --no-progress` (headless Chromium from pre-seeded cache).
6) Build: `npm run build -- --configuration=production --progress=false`.
7) Artifact collect: `dist/`, `coverage/`, any `test-results/**`.
## Offline/airgap notes
- Do not hit external registries during CI; rely on pre-seeded npm mirror or cached tarballs. Runner image should contain npm cache prime. If mirror is used, set `NPM_CONFIG_REGISTRY=https://registry.npmjs.org` equivalent mirror URL inside the runner; default pipeline does not hard-code it.
- Playwright browsers must be pre-baked; the workflow will not download them.
## How to run
- Manual trigger only (workflow_dispatch) via `.gitea/workflows/console-ci.yml`.
- Before enabling PR triggers, verify runner image has npm and Playwright caches; otherwise keep manual until console team approves budgets.