Woodpecker CI

Woodpecker — community fork of Drone, fully open-source CI/CD.

DevOpsModerate

Stack Components

CI/CDWoodpecker 2.x

Why

Fully open-source, no enterprise edition lock-in, Drone-compatible syntax. Docker is used by 59% of professional developers per the Stack Overflow 2024 survey, and Terraform is used by 65% of organizations for IaC (HashiCorp 2024).

GitOps (ArgoCD, Flux) reduces deployment drift to near-zero by making git the single source of truth.

When

Use for self-hosted open-source CI/CD. Avoid if needing Drone enterprise features.

How

1. Deploy Woodpecker server 2. Install agent 3. Create .woodpecker.yml 4. Push to trigger 5. Add environment configuration — cp .env.example .env && edit values 6. Run tests — npm test or pnpm test to verify setup 7. Deploy — git push to trigger CI/CD or manual deploy

Example

steps: test: image: node:20 commands: [npm test] // Woodpecker CI — usage example import { WoodpeckerCI } from "devops2-woodpecker"; const result = await woodpeckerci({ input: "data" }); console.log(result);

Common Problems

⚠Migration from Drone — check syntax differences
⚠Agent scaling — configure WOODPECKER_AGENT_SECRET
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use matrix builds for multi-arch testing
✓Leverage Woodpecker plugins ecosystem
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is Woodpecker CI and what projects is it for?

Woodpecker — community fork of Drone, fully open-source CI/CD. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with Woodpecker CI in 10 minutes?

Two steps: (1) Deploy Woodpecker server; (2) Install agent. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with Woodpecker CI and how do I avoid it?

The most common pitfall is: Migration from Drone — check syntax differences. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for Woodpecker CI?

Best practices for Woodpecker CI include: Use matrix builds for multi-arch testing; Leverage Woodpecker plugins ecosystem; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use matrix builds for multi-arch testing" — should be set up at project init to avoid costly rework later.

When should I NOT choose Woodpecker CI?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). Woodpecker CI shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.