Build CI Pipeline

DCD-4 Order: #4 Elaboration Has Dependencies

Updated 3 months, 3 weeks ago

APPEND TO GUIDANCE:

Release-Gated CI (Huginn Model)

For EB / release-gated projects, CI runs on published GitHub Releases (and workflow_dispatch), not every push:

on:
  release:
    types: [published]
  workflow_dispatch:

# Push to main → no CI run (intentional — human controls ship via gh release create)

Why: Prevents concurrent deploy races (UpdateEnvironment: Must be Ready) and gives explicit semver control.

Image	Registry	Deployed to EB?
Web app	ECR (private)	Yes
MCP facade / CLI tool	Docker Hub (public)	No — client-side only

Method	When
OIDC `role-to-assume`	Preferred for org repos
IAM access keys in secrets	Acceptable for single-team projects

Do not treat access keys as always wrong — document trade-off in CICD_REQUIREMENTS.md.

Design and deploy CI/CD pipeline using GitHub Actions in the application monorepo. Create Helm chart with per-environment values, add container …

No agent assigned

No rules linked.

No input artifacts