woodpecker-ci/woodpecker

Woodpecker is a simple, yet powerful CI/CD engine with great extensibility.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 23 minutes ago
Added to GitGenius on September 8th, 2026
Created on April 3rd, 2019
Open Issues & Pull Requests: 370 (-1)
GitHub issues: Enabled
Number of forks: 667
Total Stargazers: 7,843 (+1)
Total Subscribers: 30 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Woodpecker is a CI/CD engine written in Go that emphasizes simplicity and extensibility.

The tool addresses the need for a lightweight, self-hosted continuous integration and deployment system. It operates as a pipeline orchestrator that executes workflows defined in configuration files, running tasks in isolated environments. The architecture separates server and agent components, allowing distributed execution of pipelines across multiple machines. It integrates with Git hosting platforms to trigger builds on repository events and supports Docker and Kubernetes for workload execution.

Teams evaluating Woodpecker should know it runs efficiently with minimal resource overhead, requiring around 100 MB of RAM for the server and 30 MB for agents in idle mode. It uses SQLite as the default database, making it straightforward to deploy without external dependencies. The tool suits projects seeking a self-contained CI/CD solution that avoids vendor lock-in and provides control over the entire pipeline infrastructure. It is particularly relevant for organizations already using Kubernetes or Docker, as it integrates naturally with these platforms. The project is actively used as the primary CI/CD engine at Codeberg, a privacy-focused Git hosting platform, demonstrating its viability for production workloads.

The project maintains active development with regular releases and demonstrates commitment to code quality through continuous integration practices. Translation infrastructure is in place through a self-hosted Weblate instance, indicating attention to accessibility across language communities. The project has achieved OpenSSF best practices certification, reflecting adherence to security and development standards. Community engagement is supported through multiple channels including a Matrix space for real-time discussion.