woodpecker VS Airflow

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/

Contributing to Apache Airflow's open-source project immersed me in collaborative coding. Experienced maintainers rigorously reviewed my contributions, providing constructive feedback. This ongoing dialogue refined the codebase and honed my understanding of best practices.

In week Two, I contributed to the Apache Airflow repository.

Apache Airflow is an open-source platform to programmatically author, schedule, and monitor workflows. The platform features a web-based user interface and a command-line interface for managing and triggering workflows.

Airflow is the most widely used and well-known tool for orchestrating data workflows. It allows for efficient pipeline construction, scheduling, and monitoring.

AIRFLOW This is more of a library in my opinion, but Airflow has become an essential tool for scheduling in my work. All our ML training pipelines are ordered and scheduled with Airflow and it works seamlessly. The dashboard provided is also fantastic!

I agree there are many options in this space. Two others to consider:

- https://airflow.apache.org/

- https://github.com/spotify/luigi

There are also many Kubernetes based options out there. For the specific use case you specified, you might even consider a plain old Makefile and incrond if you expect these all to run on a single host and be triggered by a new file showing up in a directory…

You can try and contribute some new connectors/operators for workflow managers like Airflow or Airbyte