Restores the two browser-based zegit CI gates on the self-hosted runner (operator ask, 2026-09-08): browser tests (chromedp + CDP virtual authenticator over the WebAuthn pages) and lighthouse. Both were github.com-only jobs and have not run anywhere since ci was routed to this runner on 2026-08-31.
What changes
apk add chromium font-noto postgresql-client in the toolchain image. Nothing else.
font-noto — text must render for layout/contrast audits to mean anything.
postgresql-client — psql, so the lighthouse job can CREATE DATABASE / DROP DATABASE on ci-postgres (ZEGIT_TESTPG_DSN) instead of migrating the shared maintenance database from under the integration suite's template.
Verified
Local docker build (amd64, Alpine 3.23 base): chromium-browser 149.0.7827.53, psql 18.6, 45 font files, node v24.18.1, image still runs as uid 1000.
After merge
Dispatch build image (gitea) with tag 12.11.1-ci7 (buildkitd multi-arch, pushes to the Gitea registry).
flux-config: pin the new digest on deployment-zegit-runner.yaml and deployment-forgejo-runner.yaml (one tag for both, per the README).
zegit: drop the github.com guard on browser, add lighthouse (gitea) — prepared, pushed once the image is live so master never goes red on a missing Chromium.
Assumptions & Decisions
Image grows by ~300 MB (Chromium); accepted for a CI toolchain image.
Chromium package from the Alpine 3.23 repo the base image already tracks, not a pinned Chrome-for-Testing build (glibc, would not run on musl).
Restores the two browser-based zegit CI gates on the self-hosted runner (operator ask, 2026-09-08): `browser tests` (chromedp + CDP virtual authenticator over the WebAuthn pages) and `lighthouse`. Both were github.com-only jobs and have not run anywhere since `ci` was routed to this runner on 2026-08-31.
## What changes
`apk add chromium font-noto postgresql-client` in the toolchain image. Nothing else.
- **chromium** — chromedp finds `chromium`/`chromium-browser` on PATH; lighthouse-ci's chrome-launcher takes `CHROME_PATH`.
- **font-noto** — text must render for layout/contrast audits to mean anything.
- **postgresql-client** — `psql`, so the lighthouse job can `CREATE DATABASE` / `DROP DATABASE` on ci-postgres (`ZEGIT_TESTPG_DSN`) instead of migrating the shared maintenance database from under the integration suite's template.
## Verified
Local `docker build` (amd64, Alpine 3.23 base): `chromium-browser 149.0.7827.53`, `psql 18.6`, 45 font files, `node v24.18.1`, image still runs as uid 1000.
## After merge
1. Dispatch **build image (gitea)** with tag `12.11.1-ci7` (buildkitd multi-arch, pushes to the Gitea registry).
2. flux-config: pin the new digest on `deployment-zegit-runner.yaml` and `deployment-forgejo-runner.yaml` (one tag for both, per the README).
3. zegit: drop the github.com guard on `browser`, add `lighthouse (gitea)` — prepared, pushed once the image is live so master never goes red on a missing Chromium.
## Assumptions & Decisions
- Image grows by ~300 MB (Chromium); accepted for a CI toolchain image.
- Chromium package from the Alpine 3.23 repo the base image already tracks, not a pinned Chrome-for-Testing build (glibc, would not run on musl).
Agent-Session: db2d99bf-cb35-5418-bff1-3b0aad3ee428
zegit's `browser tests` (chromedp + CDP virtual authenticator) and
`lighthouse` jobs were github.com-only, so when `ci` was routed to this
runner on 2026-08-31 they stopped running anywhere. Chromium 149 (Alpine
3.23) with font-noto lets both run here; psql lets the lighthouse job
create and drop its own database on ci-postgres instead of migrating the
shared maintenance database from under the integration suite's template.
Verified locally (docker build, amd64): chromium-browser 149.0.7827.53,
psql 18.6, 45 font files, node 24.18.1, still uid 1000.
agent
marked the pull request as ready for review 2026-09-08 05:51:43 +00:00
markus
merged commit cada2273bb into master2026-09-08 05:52:39 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Restores the two browser-based zegit CI gates on the self-hosted runner (operator ask, 2026-09-08):
browser tests(chromedp + CDP virtual authenticator over the WebAuthn pages) andlighthouse. Both were github.com-only jobs and have not run anywhere sinceciwas routed to this runner on 2026-08-31.What changes
apk add chromium font-noto postgresql-clientin the toolchain image. Nothing else.chromium/chromium-browseron PATH; lighthouse-ci's chrome-launcher takesCHROME_PATH.psql, so the lighthouse job canCREATE DATABASE/DROP DATABASEon ci-postgres (ZEGIT_TESTPG_DSN) instead of migrating the shared maintenance database from under the integration suite's template.Verified
Local
docker build(amd64, Alpine 3.23 base):chromium-browser 149.0.7827.53,psql 18.6, 45 font files,node v24.18.1, image still runs as uid 1000.After merge
12.11.1-ci7(buildkitd multi-arch, pushes to the Gitea registry).deployment-zegit-runner.yamlanddeployment-forgejo-runner.yaml(one tag for both, per the README).browser, addlighthouse (gitea)— prepared, pushed once the image is live so master never goes red on a missing Chromium.Assumptions & Decisions
Agent-Session: db2d99bf-cb35-5418-bff1-3b0aad3ee428