What problem it solves

Woodpecker provides a CI/CD engine with extensibility through plugins. It can be installed in various ways and runs with SQLite as database by default.

Key features

• Extensible CI/CD engine — The engine is designed around extensibility and supports additional capabilities through plugins. The plugin overview includes both core-team and community-maintained plugins.

  Source: README

• Flexible installation — Woodpecker supports several installation methods. Its default database is SQLite.

  Source: README, docker-compose.example.yaml

• Server and agent components — The repository separates the server, agent, shared packages, pipeline implementation, command-line interface, and web interface into distinct areas.

  Source: server, agent, pipeline

• Multiple source-control integrations — The Go module includes integration libraries for Gitea, Forgejo, GitHub, GitLab, and Bitbucket.

  Source: woodpecker-go

• Documentation and localization — The project provides documentation and maintains a self-hosted translation platform. An overview of the current translation state is also available.

  Source: README

Who it may suit

This project may suit teams and open-source maintainers seeking an extensible CI/CD engine with a plugin ecosystem, straightforward installation options, and integrations for several source-control platforms.

Topics to discuss

• Which plugins would provide the most value for common CI/CD workflows?

• How can the plugin ecosystem make pipeline configuration easier to maintain?

• Which installation and database configuration works best for different deployment environments?

Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/woodpecker-ci/woodpecker#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.