woodpecker VS kraken

https://github.com/woodpecker-ci/woodpecker

Is anyone using woodpecker? It's a self-hosted CI/CD server forked from Drone. Really good, and actively developed.

Run your own container registry, build and host everything yourself, dont rely on others. Docker for example has a option for that but imo its very basic and limited. Harbor is more advanced but still not overly complicated. You could add build workers to that and automate your entire pipeline, but maybe for a single image thats overkill. But good to have those options in the future. Things to look at for example: Gitea (lighter) / Gitlab (more heavy), Drone.io, Woodpecker

> I wish it had some sort of CI like github actions or bitbucket pipeline

I use Gitea with Drone CI and it works pretty well: https://www.drone.io/

Some might also prefer the Woodpecker CI fork due to the license: https://woodpecker-ci.org/

I setup Drone as a part of my migration away from GitLab Omnibus and have no complaints so far: https://blog.kronis.dev/articles/goodbye-gitlab-hello-gitea-...

https://woodpecker-ci.org/ Open source clone of drone.io

https://www.drone.io/ or the more open fork https://woodpecker-ci.org/

I’m trying to migrate of my personal repos from GitHub to Codeberg. The biggest problem is to find a replacement for GitHub Actions (the free offering is so generous), and my current solution for that is to self-host an instance of Woodpecker CI [1].

I’d like to see even more diversity in Git hosting beyond “let’s all migrate from X to Y”, and for that to happen, Forgejo (a soft fork of Gitea) has already began implementing federation [2].

[1]: http://woodpecker-ci.org/

The open source version of drone is https://woodpecker-ci.org/

Kraken CI is a modern CI/CD system that operates on the Continuous Integration philosophy, focusing on pre-commit and post-commit phases in software development. In the pre-commit phase, developers and testers prepare code changes, aiming to minimize the risk of breaking production code. Kraken CI facilitates this by providing a validation environment that simplifies testing, making it easier to produce quality code. It reduces the likelihood of large, risky changes and helps manage code integration more effectively.

You could have a look on https://kraken.ci.

Kraken CI is a new Continuous Integration tool. It is a modern, open-source, on-premise CI/CD system that is highly scalable and focused on testing. It is licensed under Apache 2.0 license. Its source code is available on Kraken CI GitHub page.

Maybe have a look on https://kraken.ci. It aims to compete with Jenkins in on-prem, open-source area.

Hello, I wrote a new instalment of a series of articles about Kraken CI (https://kraken.ci). Part 3 is about autoscaling CI on AWS: https://nowikowski.medium.com/autoscaling-ci-with-kraken-ci-d1afb9d6b2c8

This is it. In this installment we learn how to clone Git repository, how to run tests using Pytest, how to install dependencies and how to build artifacts and store them in Kraken's storage. More about Kraken CI you can find on https://kraken.ci.