Docs: the Gitea runner runs the full workflow, e2e included; open question 15 resolved

Co-Authored-By: Claude Fable 5.1 <[email protected]>
2026-10-16 10:56:09 -06:00
parent 0dfe856f17
commit 6ac62c0bd0
3 changed files with 11 additions and 7 deletions
@@ -57,5 +57,6 @@ which holds the runner's own token: keep the `data` folder private (it is owned

 - The job images and the actions (`actions/checkout`, `setup-python`, `setup-node`, the docker ones) are
  fetched from docker.gitea.com, GitHub and GitHub releases, so docker-1 needs outbound internet.
- The Samba DC in the e2e stack needs `cap_add: SYS_ADMIN`. The first run on this runner shows whether the
-  Docker proxy allows it; if not, the e2e job stays a by-hand step (docs/DEPLOY.md).
+- The Samba DC in the e2e stack needs `cap_add: SYS_ADMIN`. The runner passes it through: the third run
+  (2026-10-16) brought the stack up and passed the 10 Playwright scenarios in under two minutes.
+- Timings with the cache working (run 3): server 3 min 46 s, frontend 1 min 06 s, e2e 1 min 48 s.