5 ms·
I've already jumped ship. Switching source control host was actually pretty easy. Builds still working just fine.
by anothernewdude 9mo ago
I've already jumped ship. Switching source control host was actually pretty easy. Builds still working just fine.
- thomasnno 9mo agoGreat! Who did you jump to ?
- embedding-shape 9mo agoThe most obvious "all-in-one" package is GitLab, if you have the hardware for it and don't mind bit of bloat but all the needed features in one package. Personally, for smaller scale projects that still require collaboration over the web, Gitea/Forgejo + Woodpecker CI has been a really simple, lightweight and easy to maintain solution.
- germandiago 9mo agoI am self host8ng forgejo. What can other CIs do that I could potentially need that is absent?
- embedding-shape 9mo agoIf you're using the built-in Actions/CI/whatever it's called, and it works for you, then that's great, don't try to change :) I guess I'm mostly still with Woodpecker because of having used it for years already, don't think there is anything major missing with either approaches, but was a while ago I looked deeper into it, maybe someone else here knows more (recent) details.
- ascendantlogic 9mo agoI really love Gitlab CI. I don't miss managing my own Gitlab server but I definitely prefer their CI product to actions.
- anothernewdude 9mo agoGitlab. Required very few CI/CD changes to be honest.