364d6c2278
Woodpecker v3 requires numeric repo IDs in API endpoints, not
owner/repo path segments. The old paths hit the SPA frontend
catch-all and return HTML, which downstream tools misinterpret
as auth failure (401).
- Add tools/woodpecker/_lib.sh with wp_resolve_repo_id() helper
that calls /api/repos/lookup/{owner}/{repo} to get numeric ID
- Update all 3 pipeline scripts to resolve repo ID before API calls
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Woodpecker CI Tool Suite
Interact with Woodpecker CI pipelines (list builds, check status, trigger builds).
Prerequisites
jqandcurlinstalled- Woodpecker credentials in
~/src/jarvis-brain/credentials.json
Setup
A Woodpecker API token is required. To configure:
- Go to Woodpecker CI → User Settings → API
- Generate a personal token
- Add to
credentials.json:
{
"woodpecker": {
"url": "https://ci.mosaicstack.dev",
"token": "YOUR_TOKEN_HERE"
}
}
Scripts
| Script | Purpose |
|---|---|
pipeline-list.sh |
List recent pipelines for a repo |
pipeline-status.sh |
Get status of a specific or latest pipeline |
pipeline-trigger.sh |
Trigger a new pipeline build |
Common Options
-r owner/repo— Repository (auto-detected from git remote if omitted)-f json— JSON output (default: table)-h— Show help
API Reference
- Base URL:
https://ci.mosaicstack.dev - API prefix:
/api/ - Auth: Bearer token in
Authorizationheader
Examples
# List recent builds
~/.config/mosaic/tools/woodpecker/pipeline-list.sh
# Check latest build status
~/.config/mosaic/tools/woodpecker/pipeline-status.sh
# Trigger a build on a specific branch
~/.config/mosaic/tools/woodpecker/pipeline-trigger.sh -b feature/my-branch