Skip to content

Generalize processing image deploys by mission - #13

Closed
jamesray wants to merge 7 commits into
mainfrom
jamesray/mission-buildspec-automation
Closed

jamesray wants to merge 7 commits into
mainfrom
jamesray/mission-buildspec-automation

Conversation

@jamesray

@jamesray jamesray commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

This makes processing image builds derive the mission from the CodeBuild project, use the right mission ECR/base image, and trigger the actual us-east-1 architecture project with the immutable image tag.

Rebased onto the latest main and pairs with swxsoc/sdc_aws_architecture#36.

@jamesray
jamesray force-pushed the jamesray/mission-buildspec-automation branch from f1ad238 to 030581e Compare August 27, 2026 23:17
@jamesray jamesray changed the title Generalize processing Lambda buildspec for mission deploys Generalize processing image deploys by mission Aug 27, 2026
@jamesray
jamesray marked this pull request as ready for review August 27, 2026 23:20
Copilot AI lite review requested due to automatic review settings August 27, 2026 23:20

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the CodeBuild buildspec.yml to generalize Docker image builds/deploys for the processing Lambda across missions by deriving mission context from the CodeBuild project name, selecting the corresponding base image/ECR repo, and triggering the mission-specific pipeline architecture project with an immutable image tag.

Changes:

  • Skip image push/deploy entirely for PR webhook builds.
  • Derive MISSION_NAME from the CodeBuild project name (with env override support) and select mission-specific ECR repo/base image/requirements file.
  • Trigger the corresponding build_${MISSION_NAME}_sdc_aws_pipeline_architecture project in us-east-1 with CDK_ENVIRONMENT, MISSION_NAME, LAMBDA_PIPELINE, and an immutable TAG.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread buildspec.yml Outdated
Comment thread buildspec.yml Outdated
@jamesray
jamesray requested a review from Alrobbertz August 28, 2026 18:14
@jamesray
jamesray force-pushed the jamesray/mission-buildspec-automation branch from d0b0f9e to ae0464d Compare September 1, 2026 08:57
Alrobbertz
Alrobbertz previously approved these changes Sep 1, 2026
jamesray added a commit that referenced this pull request Sep 9, 2026
Classify main, tag, and pull-request builds from CodeBuild metadata,
publish an immutable image tag alongside latest, refuse to deploy from
anything but main or a release tag, and hand off to the mission's
architecture project with MISSION, CDK_ENVIRONMENT, LAMBDA_PIPELINE,
and the exact tag just pushed. Buildspec only; the workflow and doc
edits from #13 are left out.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
jamesray added a commit that referenced this pull request Sep 9, 2026
Classify main, tag, and pull-request builds from CodeBuild metadata,
publish an immutable image tag alongside latest, refuse to deploy from
anything but main or a release tag, and hand off to the mission's
architecture project with MISSION, CDK_ENVIRONMENT, LAMBDA_PIPELINE,
and the exact tag just pushed. Buildspec only; the workflow and doc
edits from #13 are left out.

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
@jamesray jamesray closed this Sep 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants