Woodpecker CI: Lightweight Container-Native CI
Woodpecker CI is a community fork of Drone that keeps the same idea: every pipeline step runs in a container, and the whole pipeline is a YAML file in your repository.
Why self-host Woodpecker CI
Jenkins is powerful and heavy; hosted CI is metered. Woodpecker sits between them: a small Go server plus agents, configured entirely from your repository, with no plugin installation or Groovy to learn. If your builds already run in containers, the mental model is almost nothing beyond what you know.
What it does
Woodpecker CI falls into the DevOps and CI/CD category of self-hosted software. It integrates with GitHub, GitLab, Gitea, Forgejo, and Bitbucket, triggering pipelines on push, tag, or pull request. Each step declares an image and commands, steps can run in parallel or in sequence with conditional execution, secrets are managed centrally, and a plugin is just a container image, which keeps the extension model refreshingly simple.
Community traction
Woodpecker emerged after Drone’s licensing change and has become the default recommendation for lightweight self-hosted CI, particularly among people running Gitea or Forgejo.
Deployment
The server and agents deploy as Docker containers, with agents scaling horizontally across machines. Resource requirements are modest enough to run comfortably alongside other services on a single homelab host.
Alternatives
Forgejo Actions and Gitea Actions build CI into the forge itself and use GitHub Actions-compatible workflow syntax. Jenkins offers vastly more plugins at much greater weight. Drone is the upstream Woodpecker forked from.
License
Woodpecker CI is released under the Apache License 2.0.
Links
Woodpecker CI is the right size for a homelab or small team that wants real pipelines without running a Java application server.