1aa1e723f6
- pnpm build now excludes @fusion/desktop and @fusion/mobile by default (recursive build still available as pnpm build:all). Saves time on workspace-wide builds that don't need the native shells. - Hoist the per-package max-worker computation into a shared packages/core/src/__test-utils__/vitest-workers.ts util. Every vitest.config.ts now calls computeMaxWorkers(), which honors VITEST_MAX_WORKERS, FUSION_TEST_TOTAL_WORKERS, and a per-config defaultCap, clamped to cpus-1. - pnpm test sets VITEST_MAX_WORKERS=2 so the workspace run keeps total fan-out modest with --workspace-concurrency=2. - Switch dashboard vitest pool from forks to threads so jsdom/React suites share a V8 heap instead of duplicating ~500MB per worker. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
CI Status Plugin
Polls CI status for branches and provides a custom API to query results. Useful for tracking the build status of feature branches created for Fusion tasks.
Features
- Branch Tracking: Automatically tracks branches when tasks move to in-progress
- Periodic Polling: Polls CI status at configurable intervals
- Custom API: Provides REST endpoints to query branch status
- Automatic Cleanup: Stops tracking branches when tasks are completed
Installation
Option 1: Copy to plugins directory
cp -r fusion-plugin-ci-status ~/.fusion/plugins/
Option 2: Install via CLI
fn plugin install /path/to/fusion-plugin-ci-status
Configuration
Settings Reference
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
ciUrl |
string | Yes | — | Base URL for CI API |
pollIntervalMs |
number | No | 30000 |
How often to poll CI status (milliseconds) |
branchPrefix |
string | No | fusion/ |
Only poll branches with this prefix |
API Endpoints
The plugin provides the following REST endpoints at /api/plugins/fusion-plugin-ci-status:
GET /status
Returns status of all tracked branches.
{
"branches": [
{
"branch": "fusion/fn-001",
"status": "pending",
"lastChecked": "2024-01-01T00:00:00.000Z",
"url": "https://ci.example.com/builds/123"
}
]
}
GET /status/:branch
Returns status of a specific branch.
{
"branch": "fusion/fn-001",
"status": "success",
"lastChecked": "2024-01-01T00:00:00.000Z",
"url": "https://ci.example.com/builds/123"
}
If the branch is not found, returns a 404 error.
POST /refresh
Triggers an immediate CI status refresh for all tracked branches.
{
"branches": [...],
"refreshed": true
}
How It Works
- Branch Creation: When a task moves to "in-progress", the plugin creates a branch name using the configured prefix (default:
fusion/) combined with the task ID (lowercased) - CI Polling: At the configured interval, the plugin polls the CI API to get status updates for all tracked branches
- CI Integration: The plugin sends a POST request to
{ciUrl}/statuswith the list of branch names - Branch Cleanup: When a task moves to "done" or "archived", the branch is removed from tracking
CI API Integration
The plugin expects your CI system to expose a /status endpoint that accepts:
{
"branches": ["fusion/fn-001", "fusion/fn-002"]
}
And returns:
{
"statuses": [
{
"branch": "fusion/fn-001",
"status": "success",
"url": "https://ci.example.com/builds/123"
}
]
}
Supported Status Values
pending— Initial state when branch is first trackedrunning— CI is buildingsuccess— CI passedfailed— CI failedcancelled— CI was cancelled
Development
# Install dependencies
pnpm install
# Run tests
pnpm test
# Build
pnpm build
License
MIT