Woodpecker CI

Lists repositories. By default the ones the authenticated account can see in Woodpecker; with include_inactive it also lists repositories that exist in the forge but were never activated, which is where the forge_remote_id for activate_repository comes from. scope="instance" lists every repository on the server and needs an administrator.

Lists the branches of a repository, as Woodpecker sees them in the forge. Useful before trigger_pipeline, which fails with a bare 400 on a branch that does not exist.

Lists the secrets at one level — repository, organization or instance-wide. Values are never returned by Woodpecker, not even here; you get names, events and image restrictions. Note that a pipeline sees all three levels, so a name missing here may still exist one level up.

Lists the accounts known to this Woodpecker instance. Admin only. Woodpecker creates an account the first time someone logs in, so this is everyone who has ever used it, not a managed roster.

Resolves an organization name to its id — the id every other org-level call needs, including org-scoped secrets and registries.

Resolves an "owner/name" pair to a repository id. Every other repository tool takes the numeric id, and this is how you get one. A repository that exists in the forge but was never activated in Woodpecker answers 404 — use list_repositories with include_inactive to find it.

Tells Woodpecker that a repository moved to a different owner or name in the forge. It does NOT move anything in the forge — do that first, then call this so Woodpecker follows. Two-step. IMPORTANT on older instances: verified against 3.11, this endpoint performs the move and THEN answers HTTP 500 ("could not determine repo for permission") when the caller is an instance administrator. The move has happened — read the repository back with get_repository before deciding anything, and do not retry, which would move it a second time. Verified against 3.18, the call answers cleanly. Most of the time it is not needed at all: forges that send webhooks report a rename and Woodpecker follows it by itself, and calling this afterwards fails on a duplicate redirection.

Stops the server from handing new work to agents. Running pipelines finish; everything else queues up. Admin only, and instance-wide — this stops CI for everybody, and it stays paused until someone calls resume_queue. Two-step.

Re-installs the forge webhook and refreshes the stored repository data. This is the fix for "pushes no longer start a pipeline" after a repository was renamed or the Woodpecker URL changed. With scope="instance" it does that for every repository on the server, which is two-step and hits the forge API once per repository.

Runs an existing pipeline again, at the same commit and with the same config it used then. The re-run gets a new number; the original is kept. Every call is another run — a retry after a timeout starts a second one, and Woodpecker offers no idempotency key to prevent that.

Lets the server hand work to agents again. Admin only. Queued pipelines start at once, so expect a burst.

Starts the cron job's pipeline immediately, without waiting for its schedule. The schedule itself is unchanged, and the run counts as a cron event — which is the point: this is how you test that a nightly job works before waiting a night for it. Every call is another run; a retry after a timeout starts a second one.

Changes the log level of the running Woodpecker server, without a restart. Admin only. "debug" and "trace" are loud — set it back when you are done, and remember that trace logs request bodies.

Starts a pipeline manually on a branch. It runs the config as it is in that branch right now, with event "manual". A branch that does not exist is rejected with a bare 400, so check list_repository_branches first. Not idempotent and there is no way to make it so — Woodpecker has no idempotency key — so a retry after a timeout starts a second pipeline. Read list_pipelines before calling again.

Changes an agent. Admin only. no_schedule=true is the drain switch: the agent finishes its current work and takes nothing new.

Changes a cron job. Only the fields you pass are touched — including "enabled", which is how a schedule is paused without losing it.

Changes a forge configuration. Admin only, and two-step: this is the setting every login and every repository read depends on, and a wrong value locks everyone out of the instance — including whoever is fixing it.

Changes the username or password of a registry entry. The address itself cannot be changed — it is the identifier; delete and re-create instead.

Changes Woodpecker settings of a repository. Only the fields you pass are touched. Note that "trusted" grants pipelines of this repository elevated container privileges and is an administrator-only change.

Changes a secret. Only the fields you pass are touched — but "events" and "images" are replaced wholesale, not merged, so pass the complete list. Passing "value" rotates the secret.

Changes an account. Admin only. The one that matters is "admin": granting it gives full control of the instance, including every secret of every repository. Fields you do not pass are preserved.