Why does Codeberg use Woodpecker CI?
Title really, but some comments ...
I'm likely to move to Codeberg, and I like the idea of a CI system that I can run locally, without tie-in to a particular code hosting vendor. But why this over e.g. Jenkins, or whatever other systems there are these days? I'm new to Woodpecker.
Presumably because Forgejo didn't have CI support until extremely recently. And because Jenkins is trash.
Are actions gold now, last i looked they were still a bit shonky?
Probably because it's much simpler to integrate than Jenkins.
Their own CI system 'Actions' is in open alpha.
Honestly, I'm glad they didn't use Jenkins. Managing it is a convoluted mess. (I don't have experience with Woodpecker CI nor with Forgejo Actions in particular, though.)