Repolode
Submit
woodpecker-ci

woodpecker-ci/woodpecker

A self-hosted CI/CD engine that runs pipelines defined in config files in containers, with extensibility through plugins.

Open-source alternative to:GitHub ActionsGitLab CI/CDCircleCI

View on GitHubWebsite
Stars
8,039
Forks
720
Open issues
393
Last commit
7 hours ago

What is it?

Woodpecker is a continuous integration and delivery engine written in Go. Pipelines are defined as configuration files in a repository, and each step runs in its own container, so builds and tests execute in isolated, reproducible environments.

The project is split into a server and one or more agents. The server handles repositories, users and pipeline state, while agents pick up jobs and execute them. By default it uses SQLite for storage, and the server and agent together need roughly 100 MB and 30 MB of RAM at idle.

Extensibility comes from plugins, which are reusable container steps. A community-maintained overview site lists both core and third-party plugins. Codeberg uses Woodpecker as its main CI/CD engine.

Key features

  • 01Pipelines are defined in repository config files and run each step in a container.
  • 02Server and agent are separate components, so build workers can be scaled out.
  • 03Uses SQLite by default, with low idle memory use.
  • 04Extensible through reusable container-based plugins.
  • 05Installable in several ways, with documentation at woodpecker-ci.org.

Use cases

  • Running automated builds and tests for projects hosted on a self-managed Git server.
  • Setting up a self-hosted CI/CD pipeline that keeps build data on your own infrastructure.
  • Extending CI workflows with community or custom container plugins.

Quick start

  1. 1

    Follow the installation instructions in the official documentation

Things to know

  • It is self-hosted, so you must run and maintain the Woodpecker server and agents yourself.

In collections

Self-hosted appsTesting frameworks & test automation tools

Topics

#ci-cd#continuous-integration#devops#docker#kubernetes#self-hosted#automation#ci#cicd#woodpeckerci

FAQ

What is woodpecker?
A self-hosted CI/CD engine that runs pipelines defined in config files in containers, with extensibility through plugins. Woodpecker is a continuous integration and delivery engine written in Go. Pipelines are defined as configuration files in a repository, and each step runs in its own container, so builds and tests execute in isolated, reproducible environments.
Is woodpecker free to use? What license does it have?
woodpecker is open source under the Apache-2.0 license. Check the license terms before using it in commercial products.
Is woodpecker still maintained?
Actively maintained. The last commit to woodpecker was on Oct 23, 2026.
What can I use woodpecker for?
Running automated builds and tests for projects hosted on a self-managed Git server. Setting up a self-hosted CI/CD pipeline that keeps build data on your own infrastructure. Extending CI workflows with community or custom container plugins.
How do I install woodpecker?
Follow the installation instructions in the official documentation
Where can I get woodpecker?
The source code and installation instructions are on GitHub: https://github.com/woodpecker-ci/woodpecker

Summary generated by AI from the project's README. GitHub stats refresh daily.

Related projects