Continuous integration
What is Woodpecker CI? An introduction to the Woodpecker CI Project's container-based CI/CD engine
Woodpecker CI is an open-source, container-based CI/CD engine that was forked from Drone 0.8. It is described as simple, powerful, and extensible, and it is designed to be lightweight, simple, and fast. Pipeline steps run in Docker containers.
- Tool
- Woodpecker CI
- Made by
- Woodpecker CI Project
- Official site
- woodpecker-ci.org
- Category
- Continuous integration
Who makes Woodpecker CI
Woodpecker CI is made by the Woodpecker CI Project, a community-focused open-source project.
The official website is linked below.
Official website: woodpecker-ci.org
What Woodpecker CI is for
Woodpecker CI is used to run CI/CD pipelines in which each step executes in a Docker container. It supports multiple workflows per project, and those workflows can depend on each other.
The project began as a fork of Drone 0.8, created after Drone's license changed to proprietary. The project states that it is community-focused and will remain free and open source.
Who Woodpecker CI is for
The project states that Woodpecker CI is for teams already using containers in their workflow. Since every pipeline step is a container, teams that already package their tooling this way can adopt it with little change in approach.
It is also suited to people who want to self-deploy. It is lightweight enough to run on a Raspberry Pi.
Notable capabilities
Woodpecker CI keeps its feature set small and centered on containers, workflows, and plugins. The capabilities below are those the project states.
- Pipeline steps run in Docker containers.
- Multiple workflows per project are supported, and they can depend on each other.
- It can be self-deployed and is lightweight enough to run on a Raspberry Pi.
- Workflow files can be run locally with the CLI before a server is installed.
- Plugins are pipeline steps for tasks such as deploying code, publishing artifacts, and notifications.
- Plugins are pulled automatically from the agent's configured container registry.
- Drone plugins are generally supported.
How Woodpecker CI fits continuous integration
In the continuous integration category, Woodpecker CI is an engine that runs build and test steps as containers, and its plugin steps also cover deployment and publishing tasks. That puts it across both the integration and delivery sides of a pipeline.
In Deployelm's wider niche of CI/CD and deployment platforms, it represents the self-deployed, open-source option. The ability to run workflow files locally with the CLI means a pipeline can be tried before any server is set up, and support for Drone plugins is relevant to anyone coming from Drone.
Frequently asked questions
What is Woodpecker CI used for?
Woodpecker CI is a CI/CD engine that runs pipeline steps in Docker containers. It supports multiple workflows per project that can depend on each other.
Is Woodpecker CI a fork of Drone?
Yes. It was forked from Drone 0.8 after Drone's license changed to proprietary.
Does Woodpecker CI support Drone plugins?
Drone plugins are generally supported. Plugins are pipeline steps pulled automatically from the agent's configured container registry.
Can Woodpecker CI run on a Raspberry Pi?
Yes. It is lightweight enough to run on a Raspberry Pi and can be self-deployed.
Can I test Woodpecker CI workflows locally?
Yes. Workflow files can be run locally with the CLI before installing a server.
Deployelm is independent and is not affiliated with Woodpecker CI Project. Product names belong to their owners. Features change; confirm details on the official website.