# woodpecker-cli mit Homebrew, apk, Nix, pacman, zypper installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für woodpecker-cli in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:woodpecker-cli ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install woodpecker-cli ``` Evidenz: local Homebrew formula metadata ### Linux - apk (92%): ```sh sudo apk add woodpecker-cli ``` Evidenz: Alpine Linux edge package indexes: woodpecker-cli from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz - Nix (92%): ```sh nix profile install nixpkgs#woodpecker-cli ``` Evidenz: nixpkgs package indexes: woodpecker-cli from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix - pacman (92%): ```sh sudo pacman -S woodpecker-cli ``` Evidenz: Arch Linux sync databases: woodpecker-cli from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz - zypper (92%): ```sh sudo zypper install woodpecker-cli ``` Evidenz: openSUSE Tumbleweed package metadata: woodpecker-cli from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst ## Paketfakten - **Paketschlüssel:** brew:woodpecker-cli - **Paketmanager:** Homebrew - **Version:** 3.17.0 - **Quellzusammenfassung:** CLI client for the Woodpecker Continuous Integration server - **Homepage:** - **Repository:** - **Zuletzt aktualisiert:** 2026-07-31T17:39:26Z - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - woodpecker-cli (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 3.17.0 ## Projektgeschichte und Nutzung Woodpecker CLI is the command-line client for Woodpecker CI, a lightweight, container-oriented continuous integration and delivery system. The CLI is used both as an administrative client for a Woodpecker server and as a local execution tool for testing pipelines before they run on a server. Woodpecker itself is a community continuation of the open-source Drone 0.8 lineage. The Woodpecker documentation states that the project was originally forked from Drone 0.8 after Drone changed its license after that release from Apache 2.0 to a proprietary license, making Woodpecker the branch that continued from the last freely available Drone version. ### Projektgeschichte The public GitHub repository for Woodpecker was created on 2019-04-03. Its README describes Woodpecker as a simple but powerful CI/CD engine with great extensibility, and the current documentation describes it as lightweight, simple to use, and fast. That positioning reflects its origins as a smaller self-hosted CI system rather than a hosted SaaS CI product. Woodpecker inherited important ideas from Drone: pipeline definitions are container-oriented, steps run in containers, and self-hosted Git forges are central to the expected deployment model. Over time the project developed its own identity, documentation, plugin catalog, Matrix community, Open Collective sponsorship, and release stream. The CLI follows that split between server administration and local developer feedback. The current CLI manual documents global options for server and token configuration, commands for repositories, builds, registries, secrets, users, and contexts, and an `exec` command for executing a local pipeline with metadata and backend options. ### Adoptionsgeschichte Woodpecker's adoption is strongest in the self-hosted and open-source forge ecosystem. The official README says Codeberg uses Woodpecker as its main CI/CD engine, which is a notable adoption signal because Codeberg is a public Git hosting platform focused on privacy and free software development. The GitHub repository also shows substantial community traction for a self-hosted CI project, with thousands of stars and hundreds of forks. Its plugin overview and current documentation indicate a broader ecosystem of core-team and community-maintained plugins. ### Wie es verwendet wird Developers typically use `woodpecker-cli` to authenticate against a Woodpecker server, inspect repositories and builds, manage secrets and registries, or switch named contexts. CI administrators use it as a scriptable surface for operations that would otherwise happen in the web UI. A particularly package-relevant use is `woodpecker-cli exec`, which runs a pipeline locally. The current introductory docs explicitly recommend local workflow execution when a user wants to try a pipeline before installing or using a server, making the CLI useful even outside a full Woodpecker deployment. ### Warum Paket-Nerds sich dafür interessieren Woodpecker CLI matters to package users because it is the portable local handle for a self-hosted CI stack. Installing it through a package manager gives developers a stable tool for linting, dry-running, and administering CI without checking a binary into every repository. The Drone lineage is also important to packagers: Woodpecker preserves an Apache-licensed path for users who liked Drone's container pipeline model but wanted a fully open project with community governance. ### Zeitleiste - 2019-04-03: The woodpecker-ci/woodpecker GitHub repository is created. - Drone 0.8 era: Woodpecker is forked from the last Apache-licensed Drone release, according to the official Woodpecker about documentation. - 2020s: Woodpecker develops a current 3.x documentation set, plugin site, public CI instance, and CLI with local `exec` support. - 2026-07-02: GitHub API data showed active repository pushes, reflecting ongoing maintenance at the time of this enrichment run. ### Related projects - Drone CI is the direct upstream lineage through Drone 0.8. - Codeberg is a notable public Woodpecker deployment named in the official README. - Gitea, Forgejo, GitHub, and GitLab are common forge-side companions in Woodpecker deployments. ### Quellen - - - - - ## Sicherheitshinweise Für woodpecker-cli wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat. ## Andere Paketmanager-Einträge - Nix - woodpecker-cli: normalized package name match | nixpkgs package indexes: woodpecker-cli from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix - apk - woodpecker-cli - 3.16.0-r1: normalized package name match | Alpine Linux edge package indexes: woodpecker-cli from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Woodpecker Server CLI | https://woodpecker-ci.org - pacman - woodpecker-cli - 3.17.0-1: normalized package name match | Arch Linux sync databases: woodpecker-cli from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A simple CI engine with great extensibility (cli) | https://woodpecker-ci.org - zypper - woodpecker-cli - 3.16.0-1.3: normalized package name match | openSUSE Tumbleweed package metadata: woodpecker-cli from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | CLI for the WoodpeckerCI system | https://github.com/woodpecker-ci/woodpecker ## Combined YAML source View the package source record on GitHub. [combined/woodpecker-cli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/woodpecker-cli.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph