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.

20 points · 5 comments · view on lemmy.world

5 Comments

FizzyOrange@programming.dev · 16 pts · 1y (1 reply)

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

Senal@programming.dev · 2 pts · 1y

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

Kissaki@programming.dev · 3 pts · 1y (1 reply)

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 · 1 pts · 1y

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 · 1 pts · 1y

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.