I tried this last week and it wasn’t very good. It was poorly documented, and when it failed out on a simple java CI, I just went back to act.
Comment on Setting Up a Self-Hosted GitHub runner for CI/CD
EccTM@lemmy.ml 1 year ago
That’s cool. Any reason why you went with a self-hosted GitHub runner over making the full jump to a self-hosted Gitea instance + runner?
ikidd@lemmy.world 1 year ago
d_k_bo@feddit.org 1 year ago
This, but Forgejo instead of Gitea.
ikidd@lemmy.world 1 year ago
I tried this last week and it wasn’t very good. It was poorly documented, and when it failed out on a simple java CI, I just went back to act.
EccTM@lemmy.ml 1 year ago
Yeah, the Forgejo documentation was dreadful when I last looked, it really showed its origin as a Gitea replacement for people already using (and understanding) Gitea.
Cachvza@lemmy.world 1 year ago
My main reason was honestly laziness 😅 . I just went with what was quickest to set up. I also hadn’t realiced I could have two upstreams on my repo: one public-facing on GitHub (because I’m still in college and trying to build in public for future job opportunities) and another self-hosted on Gitea or GitLab for CI/CD.
That actually sounds like a great setup, so I’ll definitely look into it now. Thanks for the recommendation!