Files
stack/packages/mosaic/framework/tools/woodpecker
jason.woltje 206dbacdae
All checks were successful
ci/woodpecker/pr/ci Pipeline was successful
ci/woodpecker/push/ci Pipeline was successful
fix(framework/tools): prettier-format woodpecker README — restore main format gate
#547 merged with an unformatted README.md (prettier markdown violation),
failing the format CI step on main. Mechanical prettier --write fix only,
no content change. Restores main to green.

Refs #546
2026-06-18 17:11:47 -05:00
..

Woodpecker CI Tool Suite

Interact with Woodpecker CI pipelines (list builds, check status, trigger builds).

Prerequisites

  • jq and curl installed
  • Woodpecker credentials in ~/src/jarvis-brain/credentials.json

Setup

A Woodpecker API token is required. To configure:

  1. Go to Woodpecker CI → User Settings → API
  2. Generate a personal token
  3. 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
ci-wait.sh Block until pipeline(s) reach terminal state

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 Authorization header

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

# Block until one or more pipelines finish (event-driven CI wait)
~/.config/mosaic/tools/woodpecker/ci-wait.sh -r usc/uconnect -n 3917 -n 3918