What Codeberg's CI is, how the free Woodpecker CI-based pipeline works, how to get access, its limits, and how it fits into Codeberg.org.
Codeberg's CI runs on Woodpecker CI, an open-source, container-native pipeline engine hosted at ci.codeberg.org. Pipelines are defined in YAML files stored directly in the repository, and each step runs inside a Docker container, an approach familiar to anyone who has used Drone CI, GitLab CI, or similar container-based systems.
Because Codeberg's compute is donated and limited, only linux/amd64 builds run on the shared instance. Projects needing other architectures, more throughput, or predictable performance can attach their own self-hosted Woodpecker agents, which plug into the same Codeberg-hosted control plane.
Getting started requires filling out a request form; a Codeberg volunteer manually reviews and approves suitable use cases before granting access, a deliberate friction point meant to prevent abuse of shared resources funded by nonprofit memberships and donations.
Codeberg is upfront that the service has no SLA and can break or pause during maintenance. Role-based access control is also more limited than commercial CI products. In parallel, Codeberg has been rolling out Forgejo Actions, a GitHub-Actions-style CI system built into the Forgejo software itself, currently in limited open alpha alongside Woodpecker.
Codeberg's CI suits open-source maintainers, small self-hosted projects, and developers who prioritize European hosting and community governance over guaranteed uptime or enterprise support contracts.
It is not intended to compete with high-volume commercial CI platforms; teams with demanding concurrency or reliability needs are better served by paid providers or by attaching their own self-hosted Woodpecker agents to Codeberg's control plane.
Yes. It is funded by Codeberg e.V.'s nonprofit memberships and donations, with no paid tiers.
Woodpecker CI, an open-source, container-based pipeline engine, hosted at ci.codeberg.org.
Fill out a request form describing your use case; a Codeberg volunteer manually reviews and approves it.
Yes, Woodpecker supports self-hosted agents that teams can attach for specialized needs.
Not on the shared runners; other architectures require a self-hosted agent.
Forgejo Actions is a GitHub-Actions-style CI system built into Forgejo itself, currently in limited open alpha alongside Woodpecker.
Codeberg e.V., a German nonprofit association headquartered in Berlin, founded in 2018 with the platform launching in 2019.
No. Access is provided on an as-is, best-effort basis with no guaranteed uptime.