- Shipped
- September 23, 2026 at 6:48 AM UTC
- Author
- Kamo
- Commit
- fccd261
service-template.yaml, cloud-init.userdata.yaml and cloud-init.networkdata.yaml. They were written into a second worktree and committed from neither — the earlier hosted-computers commit was staged by pathspec from the first one, and a pathspec commit skips untracked files silently. Not a CI inconvenience: without these, ComputeService cannot render a Service for a computer (so nothing can reach its RDP port or its agent) and cannot write cloud-init (so a guest gets no account, no agent credential and no swap preparation). Every provision would have failed at the first render. Caught by scripts/sync-templates.sh refusing to continue with a template missing, which is why the image build failed loudly at that step instead of producing a jar that would have thrown at runtime — the guard earned itself here. Found by reproducing the two Maven stages in a throwaway pod on the same alpine base image, because this Forgejo stores no job logs and there is no container runtime on the box. The step list embedded in the run page had already narrowed it to "Build & push image"; the pod named the file.