# Woodpecker Agent

Woodpecker Agent is the worker component of the Woodpecker CI/CD engine that executes automated build and test jobs. It is open source and self-hosted, installable on Docker Hub and TrueNAS.

Canonical page: https://ourlocalhost.com/app/5851/woodpecker-agent

## Description

Woodpecker Agent is the worker component of the Woodpecker CI/CD engine that executes automated build and test jobs. It connects to the main Woodpecker server to perform the actual work—such as compiling code or running tests—and reports the results back. Designed for distributed environments, it allows you to offload heavy CI/CD tasks to dedicated machines.

## Platform availability

Available on 2 of 10 platforms: TrueNAS, Any server.

## Health score

81/100 (Excellent), based on 5 of 5 factors.
- Maintained: 100 (last commit 3 days ago)
- Popular: 78 (8,232 GitHub stars)
- Easy to install: 45 (2 install platforms, install notes, Docker image)
- Light to run: 100 (30 MB minimum RAM, runs on ARM)
- Security check: 68 (no serious findings, 3 minor, tests, OpenSSF Scorecard 6.3/10)

## Links

- GitHub: https://github.com/woodpecker-ci/woodpecker
- Docker Hub: https://hub.docker.com/r/woodpeckerci/woodpecker-agent
- TrueNAS: https://apps.truenas.com/catalog/woodpecker-ci
- Official website: https://woodpecker-ci.org

## Common questions

### How does a Woodpecker agent register with the server?

The agent connects to the server using the token from WOODPECKER_AGENT_SECRET when it starts. The server identifies the agent and registers it in its database if it has not connected before.

### What WOODPECKER_HOST value is required before starting Woodpecker?

Set WOODPECKER_HOST to a valid address that users and agents can reach. If it is malformed, Woodpecker exits during startup instead of running.

### Can I add my own Woodpecker agent to Codeberg without self-hosting the full CI stack?

Yes, you can add your own Woodpecker agents to your user or organization. Codeberg's shared CI resources are volunteer-run and have limitations.

### How does Woodpecker execute pipeline steps?

Woodpecker uses Docker containers to execute pipeline steps. Plugins can extend the pipeline features beyond a normal Docker image.

## Alternatives

- 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/5851/woodpecker-agent), the self-hosted and open-source app directory.
