alt Hacker NewsWe're starting to have the conversation of "do we need to replace GitHub as our CI/CD pipeline?"
No idea if/when we decide to pull that bandaid but I think once we can't merge a hot fix into main because of GH being down, it'll be a big org push to replace it.
What's everyone else using? Self hosted Gitlab? Gitea?
Replies
Self-hosted GitLab at work, self-hosted Gitea at home.
We use self-hosted Github runners, but it's a moot point if all of Github is mostly down as is the case right now. :\
Worth being upfront with, I'm an employee, but; Buildkite.
Frontier labs and global saas heavyweights run CI through us, plus a crop of open source tooling like Bazel, vLLM, Firecracker, Rails, Ray, Sorbet and Rust.
Shopify, Uber, Airbnb, Canva stresstested the platform ten years ago for scaling issues.
You need to take a little time to design upfront and take advantage of dynamically programmable primitives. It isn't the same ease/convenience as Actions. Bit more available though.
ultimately, folks need to stop writing massive YAML files to define their builds. CI should schedule jobs, your build system should define them. my workflow files look like this:
steps:
name: Do the thing
run: nix build .#
If you're seriously looking at Gitea/Forgejo, I run Fjord, dedicated managed Forgejo, so you don't have to operate it yourself. We can help with migration and runners too. We also run a free public Forgejo instance if you just want to kick the tires first.
Self-hosted GitLab and self-hosted GitLab Runners (Omnibus Docker image)
> What's everyone else using? Self hosted Gitlab? Gitea?
tangled.org!
If your app is not too large you can do CI/CD perfectly fine from your laptop. Put it in a docker container if you want to ensure it is perfectly reproducible. You still need Github as the origin repo to pull from, but the "git part" of GitHub seems to be (almost) always up and running. (We use "capistrano" for this)
Self hosted Gitlab at work with local runners
blacksmith.sh just raised tens of millions on the core premise that self-hosting CI/CD is hard [0].
they've had multiple outages in the last week, so i guess they are proving themselves correct.
in practice, giving ssh/sudo to AI (codex) and telling it to setup ephemeral self-hosted runners on your own host VM (qemu), takes about 30 minutes and works extremely well. it bangs out all the shell scripts. moved my own business over to it. zero problems.
you might even find it is kind of neat too. you can customize your VM with software pre-installed. speeds up your builds quite a bit.
[0] https://www.blacksmith.sh/blog/blacksmith-seed-announcement
TeamCity
> We're starting to have the conversation of "do we need to replace GitHub as our CI/CD pipeline?"
Did you have the conversation "do we need to move from $whatever CI/CD to GitHub Actions?" beforehand? What were the arguments in favour?