Build a ready-to-use Woodpecker CI workflow in seconds. Choose your steps, enter your commands, and copy the generated .woodpecker.yml into your repository.
Save the output as .woodpecker.yml in the root of your repository. Woodpecker picks it up on the next push.
How to Use
- Enter the Docker image your steps should run in.
- Tick the steps you need (build, test, deploy) and fill in their commands.
- Set the branch the deploy step should run on.
- Press Generate Workflow, then Copy, and save the output as .woodpecker.yml in your repository root.
Key Features
- Valid .woodpecker.yml output — steps, images and commands in Woodpecker’s expected format.
- Branch filter for deploys — run the deploy step only on your chosen branch.
- Build, test and deploy steps — include only the steps your project needs.
- 100% private — runs entirely in your browser; nothing is sent or stored.
FAQs
What is Woodpecker CI?
Woodpecker is a simple, container-based continuous integration engine and a community fork of Drone. Workflows are defined in a .woodpecker.yml file (or .woodpecker.yaml).
Where do I put the generated file?
Save it as .woodpecker.yml in the root of your repository. Woodpecker picks it up automatically on your next push.
How is Woodpecker different from Drone?
Both use the same container-native pipeline concepts. Woodpecker is community-driven, and its configuration uses named steps rather than a list of steps.
Is my data sent anywhere?
No. Everything runs entirely in your browser and never transmits or saves your entries.
Related Tools
Try these related tools: Drone CI Generator, GitLab CI Generator and GitHub Actions Generator.