Files
newsfeed/.gitea/workflows/deploy.yml
rob thijssen 62d5bc6569
Some checks failed
deploy / build-web (push) Successful in 1m27s
deploy / deploy-web (push) Successful in 4s
deploy / build-api (push) Successful in 6m16s
deploy / deploy-api (push) Failing after 30s
ci(deploy): keep deploy jobs on fedora-43 (ssh is present via git-core)
Reverts the move to `infra`. Verified on a fedora-43 runner that the ssh
reachability check ran fine (it added the host key and connected) — the
earlier deploy failure was the unprovisioned remote sudo step, not a missing
ssh client. Every runner has ssh: `git` (installed for checkout) pulls
`git-core`, which hard-requires `openssh-clients`. So fedora-43 (ssh + rsync +
curl) is the right, lighter runner for these deploy jobs.

See architecture gitea-runners.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016fKZzDpvjiJ9eYbPGgJvUP
2026-07-08 12:10:43 +03:00

5.6 KiB