woodpecker-ci/woodpecker
Woodpecker
Woodpecker is a self-hosted continuous integration server that automates building, testing, and deploying code changes triggered by repository events. It connects to a code forge to trigger pipelines on events and authenticate users, with pipelines defined in YAML files stored in the repository for version-controlled, declarative CI/CD configuration.
Each pipeline step runs in an isolated Docker container, ensuring reproducible builds and clean environments with step-level resource isolation. The system uses webhook-driven event triggering from code forge events, and supports a multi-architecture agent pool that distributes pipeline workloads across heterogeneous infrastructure. Plugin-based step extensibility allows reusable, community-contributed pipeline actions through pre-built Docker images.
The server provides database-backed state persistence for pipeline runs, logs, and metadata, enabling historical queries and audit trails. OAuth-based authentication delegates user authentication to the connected code forge, eliminating separate credential management. The system supports multi-platform build execution across different operating systems and architectures from a single configuration.
Features
- CI/CD Automation Servers - Automates build, test, and deployment workflows triggered by repository code changes.
- Forge Integrations - Connects to code hosting platforms to trigger pipelines on events and authenticate users.
- YAML-Based Task Definitions - Defines pipelines declaratively in YAML files stored in the repository.
- Container Workflow Orchestration - Defines and executes multi-step pipelines using container images for each task.
- Code Forge Connectors - Connects to code forges to trigger pipelines on events and authenticate users via OAuth.
- Pipeline Step Execution - Each pipeline step executes in an isolated Docker container for reproducible builds.
- Continuous Integration Servers - Automates building, testing, and deploying code changes triggered by repository events.
- Self-Hosted Infrastructure - Deploys and manages the CI/CD system on your own servers for full control.
- Event-Driven Webhooks - Triggers pipelines automatically via webhooks from code forge events.
- OAuth Authentication - Delegates user authentication to the connected code forge via OAuth 2.0 flows.
- Database-Backed Persistence - Persists pipeline runs, logs, and metadata in a relational database for audit trails.
- Multi-Platform Build Orchestrators - Runs pipelines across different operating systems and architectures from a single configuration.
- Multi-Architecture Agent Pools - Supports distributing pipeline workloads across agents on different architectures and platforms.
- Step-Level Resource Isolation - Each pipeline step runs with its own filesystem and network namespace for clean environments.
- Plugin-Based Architectures - Extends pipeline steps with reusable, community-contributed Docker images as plugins.
- Continuous Integration - Container-based CI/CD platform for automated pipelines.
- Source Control and CI/CD - Executes CI/CD pipelines with high extensibility.
