4 ms·
When you self host, what happens with your compute costs? CI can be super expensive depending upon your test pipeline. Do you end up spending more than you woul
by newswasboring 1mo ago
When you self host, what happens with your compute costs? CI can be super expensive depending upon your test pipeline. Do you end up spending more than you would with GitHub actions for example?
- Maxion 1mo agoHuh? The VPS boxes have a fixed monthly fee
- applidhumanco 1mo agoHe is likely referring to the CI runners. Gitea has their own version of Actions runner. It is very much usable, though currently inferior to GitHub Actions (not always a 1:1 replacement, even though they aim for it to be): https://docs.gitea.com/usage/actions/ https://docs.gitea.com/usage/actions/ Cost as always depends on your usage, but it will likely be less than your current cost of GitHub Actions.
- newswasboring 1mo agoThank you. This is exactly what I meant. I work for a large company where our testing budget is massive and most of it goes towards these CI runners. Provisioning enough and consistent compute for testing pipelines sometimes becomes the bane of my existence.
- Maxion 1mo agoI can recommend that you self-host Jenkins on another box.
- JoshStrobl 1mo agoJust get some x86 and ARM runners off netcup, manage Woodpecker CI + Woodpecker Agent. Generally pretty hands-off once you get it set up. That plus a cheap VPS running Forgejo with postgres off-site backups, you are looking at a small fraction of the cost compared to per-seat GitHub pricing for orgs + Action Minutes.