Woodpecker CI

Woodpecker CI is a self-hosted continuous integration and continuous delivery (CI/CD) engine that runs automated build, test, and deploy pipelines triggered…

  • Development
  • Productivity
Woodpecker CI is a self-hosted continuous integration and continuous delivery (CI/CD) engine that runs automated build, test, and deploy pipelines triggered by changes in your Git repositories.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
100last commit 17 days ago
Popular
788,108 GitHub stars
Easy to install
150 install platforms, install notes
Light to run
100130 MB minimum RAM

Availability: links checked today

GitHub stars
8,108
Open issues
372
Last commit
2026-11-04
Latest release
v3.20.1
License
Apache-2.0
Activity
rising

Checked 17 days ago - source: GitHub (woodpecker-ci/woodpecker)

Resources & Compatibility

Minimum requirements: 130 MB RAM, 2 CPU core(s).

Checked 45 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Fill in the server settings file Copy /etc/woodpecker/woodpecker-server.env.example to /etc/woodpecker/woodpecker-server.env and set your site address, GitHub OAuth client/secret (the login credentials Woodpecker uses to let users sign in), and a random agent secret. Without these, Woodpecker can’t log you in or securely communicate with its runner. source
  • Match the agent secret and server address Copy /etc/woodpecker/woodpecker-agent.env.example to /etc/woodpecker/woodpecker-agent.env and use the same agent secret plus the server’s address and port, such as localhost:9000. If these don’t match, the agent can’t connect and pipelines will not run. source
  • Install the server and agent binaries Extract the downloaded Woodpecker server and agent tarballs for your computer’s architecture and copy the binaries to /usr/local/bin. If the files are missing or the architecture is wrong, the services won’t start correctly. source
  • Database Runs with SQLite as the database by default; no external database server is required. source

Fetched 43 days ago - each note links to its source

Alternatives (7)

  • Azure DevOps - Continuous Delivery Services for teams to share code, track work, and ship software – for any language, all in a single package.
  • CircleCI - CircleCI provides development teams the confidence to build, test, and deploy—quickly and consistently—across numerous platforms.
  • GitHub Actions - An experimental Docker image that runs self-hosted GitHub Actions runners with Docker support for CI teams whose jobs require containers.
  • GitLab - GitLab is a self-hosted Git repository server and software delivery platform for individuals and teams to privately plan, version, build, t…
  • Harness.io - Harness is a self-service CI/CD platform that allows engineers and DevOps to build, test, deploy, and verify software, on-demand.
  • Jenkins - Jenkins is a fork of Hudson and is a continuous build system for software projects.
  • semaphore - Semaphore is a modern web interface for managing DevOps tools such as Ansible, Terraform, OpenTofu, and PowerShell.

Checked 54 days ago - source: AlternativeTo

Common questions

How do I debug a Woodpecker pipeline that cannot clone the Git repository?

Get the container ID from docker ps and enter that container with docker exec -it <ID> bash. Then rerun the clone commands from the failing pipeline to reproduce the error.

Why did Woodpecker CI start from Drone CI?

It is based on an earlier version of Drone CI. Drone's license changed from Apache 2 to a proprietary license after the 0.8 release.

How can I extend Woodpecker beyond standard Docker images?

Woodpecker uses Docker containers to execute pipeline steps, and plugins can be created when a normal Docker image is not enough.

Answers sourced from forum.cloudron.io, woodpecker-ci.org, woodpecker-ci.org

Community

Collected 48 days ago - public community threads