Woodpecker CI

A simple, container-native CI/CD engine with great extensibility. Woodpecker uses pipeline-as-code — define your build, test, and deploy steps in a .woodpecker.yaml file inside your repository. Pipelines run in isolated containers for reproducibility and security.

What You Can Do After Deployment

1. Visit your domain — open the Woodpecker web UI
2. Connect a Git forge — configure a GitHub, Gitea, Forgejo, GitLab, or Bitbucket OAuth application and link it to Woodpecker via environment variables
3. Activate a repository — select which repos Woodpecker should watch for push and pull request events
4. Add a pipeline file — commit a .woodpecker.yaml to your repo to define build steps
5. Push and watch — every push triggers a pipeline; view logs and status in the dashboard

Key Features

• Pipeline-as-code with multi-step YAML definitions
• Container-native — every step runs in its own Docker container
• Git integration with GitHub, GitLab, Gitea, Forgejo, and Bitbucket
• Plugin ecosystem for notifications, deployments, and more
• Matrix builds and conditional execution
• Secrets management for credentials
• Multi-platform support (amd64, arm64)
• Lightweight — built with Go, uses SQLite by default

Important Notes

• This template deploys the Woodpecker Server only. You need a separate Woodpecker Agent to execute pipelines.
• To connect a Git forge, set the appropriate OAuth environment variables (e.g., WOODPECKER_GITHUB, WOODPECKER_GITHUB_CLIENT, WOODPECKER_GITHUB_SECRET).

License

Apache-2.0 — GitHub | Website