Hacker News Reader

Comment by embedding-shape | Hacker News Reader

Self-hosted $whatever, managed your way. CI/CD doesn't have to be dog-slow or ever go down when you need it, only when you do your upgrades yourself, as god intended it.

I personally use Forgejo + their built-in Actions stuff (mostly GitHub compatible), have one old Linux desktop as a server which runs Linux + Windows runners, one Mac Mini for macOS/iOS builds, using NixOS so I don't have to remember how things work, and it just keeps running 24/7, always there when I need it.

View on HN

There's something to be said for the social availability that github brings. I'm far more likely to submit a pr for a bugfix to a project on gh than a random self-host site.

You can do your own ci/cd runner system, but you still rely on webhooks or triggers, when you aren't hosting the code.

> There's something to be said for the social availability that github brings. I'm far more likely to submit a pr for a bugfix to a project on gh than a random self-host site.

Yeah, that used to be the single favorable argument for GitHub, nowadays I think it might be the opposite, at least personally. If the contributor can't be arsed to join the community proper (and maybe get a sign-in code to their email, or whatever login you use), I think I prefer life without their drive-by PRs.

Here is the thing, we have self-hosted runners running behind our firewall and even those go down for these kinds of outages. All the jobs just sit in the queue and are never sent to our self-hosted setup at all.

> we have self-hosted runners running behind our firewall and even those go down for these kinds of outages

Sounds like it's not as self-hosted as you think, or you have some other unnecessary dependency on something here? As long as GitHub isn't the sole place for your SCM, why would your self-hosted CI runners go down just because GitHub goes down?

because github stops passing out the jobs in general. The self hosted runners are behind the actions runner controller: https://github.com/actions/actions-runner-controller

I see, you're still using GitHub for SCM? Then I understand why it stops working :P When I said "Forgejo + their built-in Actions stuff" I meant you use Forgejo for git too, not just self-hosting runners but then connecting them to someone else's infrastructure.

If you're already hosting the runners, why not host git too? It's even simpler than running your own workers/runners.

1. Why isn't observability setup to monitor the queue depth and alert?

2. Why aren't the CI runners self-healing?

1. we absolutely have these alerts and i get alerted, often before github updates their status page updated telling me about the actions failure.

2. because when github's actions api is down in certain, seemingly very common, ways even self hosted runners can't pick up the jobs

Reply on news.ycombinator.com