Postgres until now has been using cirrus-ci for CI. Unfortunately they're shutting down June 1st.
They had been a good fit for us because:
- some free credits so everyone could run some CI on their own
- supported providing own compute for more demanding cases (via GCP and self hosted mac HW)
- jobs ran in one-off VMs
- support for custom images allowed us to pre-install everything, keeping test times manageable
- VMs not containers was good for perf
- CI job definitions could be run locally
@WoodpeckerCI might be an option
@Cs137 @AndresFreundTec @WoodpeckerCI
seems like codeberg may be a good place to go, since they'd host you free, being an opensource project, and they use woodpecker
@Viss @Cs137 @WoodpeckerCI
I suspect our CI usage would very quickly make codeberg not like us, it's probably too much given their size.
Looks like woodpecker doesn't quite have the support for running full VMs, but I guess they do have a plugin architecture for that...
@AndresFreundTec @Viss @Cs137 @WoodpeckerCI @Codeberg
I'm pretty sure both Woodpecker and Forgejo Actions allow for self-hosted runners. That would shift the cost from codeberg to you, but it sounds like that wouldn't be a problem.
We currently have no native VM support, but this is only because of some open implementation questions: https://github.com/woodpecker-ci/woodpecker/discussions/2302#discussioncomment-6775117
feedback is welcome!
And writing a own backennd is easy and transparent to the server (so you could use #codeberg 's hosted CI and use own agents with custom backend ;) )
(You just have to implement this interface: https://github.com/woodpecker-ci/woodpecker/blob/main/pipeline/backend/types/backend.go)
AndresFreundTec
Schreini
Viss
Max Nordlund
Woodpecker CI