woodpecker

> including CI pipeline You'll want to be cautious, because readme and promises are not software; they're attempting to squat on[1] nektos/act[2] which itself is the 20/80 of GitHub Actions You'll almost certainly be happier using woodpecker[3] or some other "external" CI system so you don't have to hopes-and-prayers your CI system 1: https://code.forgejo.org/forgejo/act 2: https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#... and https://codeberg.org/forgejo/forgejo/src/tag/v10.0.3/go.mod#... 3: https://github.com/woodpecker-ci/woodpecker (Apache 2)

https://docs.gitea.com/usage/actions/overview https://github.com/agola-io/agola https://github.com/concourse/concourse https://github.com/theSage21/jaypore_ci https://github.com/woodpecker-ci/woodpecker

> We have been looking for this moment for more than a year, since we installed our own hardware in Berlin. We are running Woodpecker CI, Codeberg Pages, Weblate Translate and more on it. But the heart of Codeberg – Gitea – is still on a rented cloud instance. Huh, I haven't really heard of anyone running Woodpecker CI out in the wild personally, so this is a nice thing to hear about. From what I can tell, it was a fork from Drone CI due to licensing concerns and whatnot, it appears that their repository has been a bit more active than that of Drone: https://github.com/woodpecker-ci/woodpecker/pulse/monthly https://github.com/harness/drone/pulse/monthly I wonder whether it's going to be a Gogs vs Gitea situation, since I'm still running Drone for my own needs (though it is both simple and stable, as well as suitable for my needs at this t

I am not hating on the whole of YAML, but the way they are misusing it in Woodpecker. None of those other services you mention are doing something this bad, e.g. relying on parts of YAML that are NOT standard (ordering of elements in a dict) and not supported by some languages/libraries. > From what I’ve seen, the config uses dictionaries for concurrent pipelines. You are wrong about that, see https://github.com/woodpecker-ci/woodpecker/issues/771

Yeah the docs are lacking. The way Woodpecker works is, there is a Server, that is sort of the "manager"; you only run one of these. You run one Agent on each host that you want builds to happen on. The Agent then executes the steps of your Pipeline on a "platform", which is an Agent running on a particular OS. By default an Agent just wants to execute jobs in a Docker container, using the docker backend. But there are multiple backends. To run a build on Windows/MacOS, you would download the Go binary for the Agent for that platform, and execute it with the right environment variables to specify the local backend. I think a lot of this functionality is just now getting added to Woodpecker so it's not been documented. It's been in Drone for a long time, but the fork is from a while ago. https://woodpecker-ci.org/docs/administration/setup

I mean the currently available 2.X set of versions: https://docs.drone.io/server/provider/gitea/ Its source code is also available on GitHub: https://github.com/harness/drone/releases Of course, the point about their license is a good one, which definitely has some limitations on what you can do with it: https://github.com/harness/drone/blob/master/LICENSE (I wish I earnt 5 million $ and this would be a problem I'd have to think about). Thanks for bringing up Woodpecker, though, it also seems like a nice project and the two CI solutions haven't diverged far enough for migrating over from one to another to be too problematic, should that become relevant in the future: https://github.com/woodpecker-ci/woodpecker Of course, as I said, some folks might also prefer something like Jenkins or another CI solution. I'm yet to explore most of the p