Story (Required)

As a developer, I want to run my application builds through Shipwright, orchestrated by the MCP Server, so that I can reliably produce container images with compliance, observability, and automation built in.

Background (Required)

The combination of Shipwright + MCP ensures that builds are:

• Automated (triggered and verified by MCP).

• Observable (logs, metrics, and outcomes are surfaced).

• Compliant (metadata, provenance, signing, and audit trails included).

• Scalable (orchestrated across multiple teams and clusters).

This story brings together the build engine (Shipwright) with the orchestration brain (MCP), enabling developers, operators, and release engineers to have a consistent, automated, and enterprise-ready build experience inside OpenShift.

Out of scope

<Defines what is not included in this story>

Approach (Required)

The MCP Server will act as the orchestrator for Shipwright builds by:

• Generating the required Shipwright build resources (e.g., Build and BuildRun CRDs).

• Verifying resource creation and execution.

• Collecting logs, metrics, and pass/fail results.

• Ensuring provenance and compliance metadata are attached to every build.

This story will ensure a developer can trigger a build (via CLI, API, or Git push) and MCP will handle the lifecycle management of the Shipwright pipeline without manual intervention.

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met