Why does Codeberg use Woodpecker CI?
from staircase@programming.dev to programming@programming.dev on 26 May 2025 15:31
https://programming.dev/post/31068229

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.

#programming

threaded - newest

FizzyOrange@programming.dev on 26 May 2025 16:10 next collapse

Presumably because Forgejo didn’t have CI support until extremely recently. And because Jenkins is trash.

Senal@programming.dev on 27 May 2025 05:52 collapse

Are actions gold now, last i looked they were still a bit shonky?

Kissaki@programming.dev on 27 May 2025 07:49 next collapse

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.)

staircase@programming.dev on 02 Jun 2025 23:50 collapse

I’m torn between using woodpecker and trying out their new CI. I love the idea of no vendor tie-in, but I also want an easy time

mesamunefire@piefed.social on 30 May 2025 16:38 collapse

It works. You have to ask them for permission if last I checked. You can also just run your own and use actions from the gitea system.