Roadmap: automated CI/CD deploy pipeline (pro-tier feature)

0 Anchors

— Blast radius

— Churn 30d

0 Proposals

Context

Split out from production-readiness #159, which is now closed. #159 covered getting MuseHub's own staging/production deploys to a solid manual baseline (blue/green, health-gated, tested rollback) — that's done and was sufficient for launch.

The larger automation ask from #159 — trigger-on-merge deploys, a real job-runner client, OIDC-style short-lived credentials instead of long-lived IAM keys, production approval gates, deploy notifications, structured deploy records (artifact digest/migration version/deployer/timestamp), concurrent-deploy locking — is not just internal ops tooling. It's the same underlying infrastructure as MuseHub's planned pro-tier CI/CD feature: letting MuseHub users configure automated build/test/deploy pipelines for their own repos, hosted and run by MuseHub.

Why this is its own roadmap item, not production-readiness debt

Building a one-off internal-only automation pipeline now (just to satisfy our own staging/prod deploys) would duplicate the real work once the actual customer-facing feature gets designed and built. Better to build it once, as the real product feature, and have MuseHub's own deploys be an early/first user of it rather than a separate bespoke system.

musehub-runner container exists as scaffolding for a job-execution client but was never actually built out (see Section 9 CI-pipeline research, and docs/infrastructure.md's note that it's deliberately not running in production for exactly this reason)
muse hub webhook create already exists as a plausible trigger mechanism to build on
MuseHub already has a release primitive (muse release add / muse hub release create) that could serve as the explicit production release trigger once this is designed

Not scoped yet

This issue is a placeholder to make sure the intent isn't lost — actual design (pricing tier boundaries, what's free vs. pro, UI/UX for configuring pipelines, security model for running arbitrary user build steps, etc.) hasn't started.

◎ Activity

●

gabriel opened this issue 2 days ago

◎

No activity yet. Use the CLI to comment.

Assignee

○ unassigned

Release

no commits linked to this issue

create

muse hub issue create \
  --title "..." \
  --body "..." \
  --label bug \
  --anchor path/to/file.py::Symbol \
  --commit-anchor <sha> \
  --repo gabriel/musehub

read

muse hub issue get 173 --json
muse hub issue list --state open --json

update

muse hub issue edit 173 \
  --anchor path/to/file.py::Symbol \
  --repo gabriel/musehub

comment

muse hub issue comment 173 \
  --body "Fixed in <sha>" \
  --repo gabriel/musehub

muse hub issue close 173 \
  --repo gabriel/musehub

create

create_issue({
  repo_id: "sha256:a265796360c3b1b8700b5682ced5f6b044a2c0d3a2c58918892a5aa494db6c75",
  title: "...",
  body: "...",
  labels: ["bug"],
  symbol_anchors: [
    "path/to/file.py::Symbol"
  ],
  commit_anchors: ["<sha>"]
})

read

get_issue({
  repo_id: "sha256:a265796360c3b1b8700b5682ced5f6b044a2c0d3a2c58918892a5aa494db6c75",
  issue_number: 173
})

list_issues({
  repo_id: "sha256:a265796360c3b1b8700b5682ced5f6b044a2c0d3a2c58918892a5aa494db6c75",
  state: "open"
})

update

edit_issue({
  repo_id: "sha256:a265796360c3b1b8700b5682ced5f6b044a2c0d3a2c58918892a5aa494db6c75",
  issue_number: 173,
  symbol_anchors: ["path/to/file.py::Symbol"]
})

comment

create_issue_comment({
  repo_id: "sha256:a265796360c3b1b8700b5682ced5f6b044a2c0d3a2c58918892a5aa494db6c75",
  issue_number: 173,
  body: "..."
})

close_issue({
  repo_id: "sha256:a265796360c3b1b8700b5682ced5f6b044a2c0d3a2c58918892a5aa494db6c75",
  issue_number: 173
})

create

curl -X POST \
  http://localhost:10003/api/repos/sha256:a265796360c3b1b8700b5682ced5f6b044a2c0d3a2c58918892a5aa494db6c75/issues \
  -H "Content-Type: application/json" \
  -H "Authorization: MSign handle=\"...\" ts=... sig=\"...\"" \
  -d '{
    "title": "...",
    "body": "...",
    "labels": ["bug"],
    "symbol_anchors": ["path/to/file.py::Symbol"]
  }'

read

# get one issue
curl http://localhost:10003/api/repos/sha256:a265796360c3b1b8700b5682ced5f6b044a2c0d3a2c58918892a5aa494db6c75/issues/173

# list open issues
curl "http://localhost:10003/api/repos/sha256:a265796360c3b1b8700b5682ced5f6b044a2c0d3a2c58918892a5aa494db6c75/issues?state=open"

update

curl -X PATCH \
  http://localhost:10003/api/repos/sha256:a265796360c3b1b8700b5682ced5f6b044a2c0d3a2c58918892a5aa494db6c75/issues/173 \
  -H "Content-Type: application/json" \
  -H "Authorization: MSign handle=\"...\" ts=... sig=\"...\"" \
  -d '{"title": "...", "body": "..."}'

comment

curl -X POST \
  http://localhost:10003/api/repos/sha256:a265796360c3b1b8700b5682ced5f6b044a2c0d3a2c58918892a5aa494db6c75/issues/173/comments \
  -H "Content-Type: application/json" \
  -H "Authorization: MSign handle=\"...\" ts=... sig=\"...\"" \
  -d '{"body": "Fixed in <sha>"}'

curl -X POST \
  http://localhost:10003/api/repos/sha256:a265796360c3b1b8700b5682ced5f6b044a2c0d3a2c58918892a5aa494db6c75/issues/173/close \
  -H "Authorization: MSign handle=\"...\" ts=... sig=\"...\""

Roadmap: automated CI/CD deploy pipeline (pro-tier feature)

Context

Why this is its own roadmap item, not production-readiness debt

Related existing scaffolding

Not scoped yet