mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Orchestrator: Add Woodpecker CI integration for pipeline monitoring #344

New Issue
Closed
opened 2026-02-06 17:50:34 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-02-06 17:50:34 +00:00
Owner
Copy Link

Problem

The orchestrator completes work and pushes to remote, but has no visibility into CI pipeline status. When pipelines fail, there's no automated way to:

  1. Detect the failure
  2. Fetch pipeline logs
  3. Diagnose and fix issues

Proposed Solution

Add CI integration to the orchestrator protocol:

  1. Pipeline Status Check - After git push, check pipeline status
  2. Wait for Completion - Poll until pipeline completes or times out
  3. Fetch Logs on Failure - If pipeline fails, fetch logs
  4. Auto-Diagnose - Parse logs to identify common failures (lint, type, test, build)

Implementation Options

Option A: Add Woodpecker commands to @mosaic/cli-tools
Option B: Add CI verification step to orchestrator execution loop

Acceptance Criteria

  • Orchestrator can check pipeline status after push
  • Orchestrator can fetch logs on failure
  • Orchestrator can auto-fix common CI failures
  • Works with Woodpecker CI (primary) and GitHub Actions (future)

Context

Discovered during M6 milestone - 4h18m autonomous run completed but CI failing.

## Problem The orchestrator completes work and pushes to remote, but has no visibility into CI pipeline status. When pipelines fail, there's no automated way to: 1. Detect the failure 2. Fetch pipeline logs 3. Diagnose and fix issues ## Proposed Solution Add CI integration to the orchestrator protocol: 1. **Pipeline Status Check** - After git push, check pipeline status 2. **Wait for Completion** - Poll until pipeline completes or times out 3. **Fetch Logs on Failure** - If pipeline fails, fetch logs 4. **Auto-Diagnose** - Parse logs to identify common failures (lint, type, test, build) ## Implementation Options **Option A:** Add Woodpecker commands to @mosaic/cli-tools **Option B:** Add CI verification step to orchestrator execution loop ## Acceptance Criteria - [ ] Orchestrator can check pipeline status after push - [ ] Orchestrator can fetch logs on failure - [ ] Orchestrator can auto-fix common CI failures - [ ] Works with Woodpecker CI (primary) and GitHub Actions (future) ## Context Discovered during M6 milestone - 4h18m autonomous run completed but CI failing.
jason.woltje added the orchestrator label 2026-02-06 17:50:34 +00:00
jason.woltje added this to the M6-AgentOrchestration (0.0.6) milestone 2026-02-06 18:53:29 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label orchestrator
Milestone
No items
No Milestone M6-AgentOrchestration (0.0.6)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#344
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?