Follow-on to #143. The main deploy after #145 failed on Deploy Dashboard and Deploy MCP: because compliance-agent (a workspace member) depends on the private tramiton-core git repo, cargo/dx resolves it even when building the dashboard or mcp — and those Dockerfiles had no git auth (unknown SSH host key). Deploy Agent succeeded (its #143 fix works).
Applies the same BuildKit-secret auth to Dockerfile.dashboard (dx build) and Dockerfile.mcp (cargo build), and passes the secret in the deploy-dashboard/deploy-mcp jobs. Dockerfile.docs is node-only and unaffected. Self-tests on merge (both Dockerfiles changed → both deploys run).
Follow-on to #143. The main deploy after #145 failed on **Deploy Dashboard** and **Deploy MCP**: because `compliance-agent` (a workspace member) depends on the private `tramiton-core` git repo, cargo/dx resolves it even when building the dashboard or mcp — and those Dockerfiles had no git auth (`unknown SSH host key`). **Deploy Agent succeeded** (its #143 fix works).
Applies the same BuildKit-secret auth to `Dockerfile.dashboard` (dx build) and `Dockerfile.mcp` (cargo build), and passes the secret in the deploy-dashboard/deploy-mcp jobs. `Dockerfile.docs` is node-only and unaffected. Self-tests on merge (both Dockerfiles changed → both deploys run).
The main deploy after #145 failed on Deploy Dashboard and Deploy MCP: because
compliance-agent (a workspace member) depends on the private tramiton-core git
repo, cargo/dx must resolve it even when building the dashboard or mcp — and
those Dockerfiles had no git auth ("unknown SSH host key"). Deploy Agent (fixed
in #143) succeeded.
Apply the same BuildKit-secret fix to Dockerfile.dashboard (dx build) and
Dockerfile.mcp (cargo build), and pass the secret in the deploy-dashboard and
deploy-mcp jobs. Dockerfile.docs is node-only and unaffected.
Refs #118.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
sharang
merged commit 9ec07ff7a1 into main2026-07-12 21:52:39 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-on to #143. The main deploy after #145 failed on Deploy Dashboard and Deploy MCP: because
compliance-agent(a workspace member) depends on the privatetramiton-coregit repo, cargo/dx resolves it even when building the dashboard or mcp — and those Dockerfiles had no git auth (unknown SSH host key). Deploy Agent succeeded (its #143 fix works).Applies the same BuildKit-secret auth to
Dockerfile.dashboard(dx build) andDockerfile.mcp(cargo build), and passes the secret in the deploy-dashboard/deploy-mcp jobs.Dockerfile.docsis node-only and unaffected. Self-tests on merge (both Dockerfiles changed → both deploys run).