Getting started
A Woodpecker deployment consists of two parts:
- A server which is the heart of Woodpecker and ships the web interface.
- Next to one server, you can deploy any number of agents which will run the pipelines.
Each agent is able to process one workflow by default. If you have 4 agents installed and connected to the Woodpecker server, your system will process four workflows (not pipelines) in parallel.
You can add more agents to increase the number of parallel workflows or set the agent's WOODPECKER_MAX_WORKFLOWS=1 environment variable to increase the number of parallel workflows per agent.
Which version of Woodpecker should I use?
Woodpecker is having two different kinds of releases: stable and next.
Find more information about the different versions here.
Hardware Requirements
Below are minimal resources requirements for Woodpecker components itself:
| Component | Memory | CPU |
|---|---|---|
| Server | 200 MB | 1 |
| Agent | 32 MB | 1 |
Note, that those values do not include the operating system or workload (pipelines execution) resource consumption.
In addition you need at least some kind of database which requires additional resources depending on the selected database system.
Installation
You can install Woodpecker on multiple ways. If you are not sure which one to choose, we recommend using the docker-compose method for the beginning:
- Using docker-compose with the official container images
- Using Kubernetes via the Woodpecker Helm chart
- Using binaries, DEBs or RPMs you can download from latest release
- Or using a third-party installation method
Database
By default Woodpecker uses a SQLite database which requires zero installation or configuration. See the database settings page if you want to use a different database system like MySQL or PostgreSQL.
Forge
What would be a CI/CD system without any code? By connecting Woodpecker to your forge like GitHub or Gitea you can start running pipelines on events like pushes or pull requests. Woodpecker will also use your forge for authentication and to report back the status of your pipelines. See the forge settings to connect it to Woodpecker.
Configuration
Check the server configuration and agent configuration pages to see if you need to adjust any additional parts and after that you should be ready to start with your first pipeline.
Agent
The agent is the worker which executes the workflows. Woodpecker agents can execute work using a backend like docker or kubernetes. By default if you choose to deploy an agent using docker-compose the agent simply use docker for the backend as well. So nothing to worry about here. If you still prefer to adjust the agent to your needs, check the agent configuration page.