chore(ci): drop Forgejo Actions CI, verify manually on the target VM (T-014) #2
Loading…
Reference in a new issue
No description provided.
Delete branch "ci/T-014-forgejo-ci"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Ce que fait cette PR :
buildpasse :README.md jamais copie avant le build du package (Hatchling), et collision de nom entre
l'utilisateur
operatorcree et le groupe systeme Debian du meme nom..forgejo/workflows/ci.yml. Le runner Forgejo Actions partage son reseauDocker avec
forgejo/Postgres ; le churn de conteneurs de job y rend le DNS embarquede Docker intermittemment defaillant (
server misbehavingsurlookup db), au pointde casser le push git lui-meme a deux reprises pendant le diagnostic. Voir
docs/DECISIONS.mdADR-0011 pour le detail et les alternatives ecartees.scripts/check.sh, build image, suite d integration) se fontdesormais a la main, par un humain ou par Claude Code en session sur la VM cible.
python:3.12-slim already ships a system group named "operator" (Debian legacy, GID 37). `useradd --create-home operator` tries to create a same-named group for the new user and fails on the collision ("group operator exists"). Skip that with --no-user-group, put the user in nogroup instead. Verified locally: image builds, smoke test (import hermes_operator; print __version__) passes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018bhEDzC3DQP1NFsBfMhrd6The runner's job containers share the "forge" Docker network with forgejo/Postgres. That churn makes Docker's embedded DNS resolver intermittently misbehave under load ("server misbehaving" on lookup db), which broke build/integration and, twice during this same session, git push itself (the pre-receive hook depends on the same resolution for its internal callback). See docs/DECISIONS.md ADR-0011 for the full writeup and the alternatives considered. Remove .forgejo/workflows/ci.yml. Checks (ruff, mypy, pytest, image build, integration suite) now run manually via scripts/check.sh, by a human or by Claude Code running directly on the target VM — no more push/PR-triggered automation. T-014 is closed as abandoned rather than completed as originally scoped. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018bhEDzC3DQP1NFsBfMhrd6ci(forgejo): mount docker socket into build/integration jobs (T-014)to chore(ci): drop Forgejo Actions CI, verify manually on the target VM (T-014)