Epic Goal

Provide a CLI tool to migrate BuildConfig builds to Shipwright

Why is this important?

• Customers that heavily use BuildConfig builds today need to automate the migration to Shipwright.

Context

When this Epic was created, team wanted to create a new migration CLI tool. Then we discovered an existing Openshift migration tool called Crane. We worked closely with migration team and they built out a POC to test this idea. Here is the presentation created by migration team

PPT Link: https://docs.google.com/presentation/d/1ZhxSvoLFtc69gkSKHIFXtPtcDwaOAYq3hjpeifNm9IM/edit?slide=id.g367e88771d4_0_5447#slide=id.g367e88771d4_0_5447

This PPT also has a migration demo video

Here is another document we created to review the POC

Review POC doc link: https://docs.google.com/document/d/1ufPcm5_qvZmUvJeknDN9RKyla2HKp828RJEn3azmJB0/edit?tab=t.0

Use this document to track progress of the Epic
https://docs.google.com/document/d/1UF1YBoVUEw9dwhX9YH7Au6kHOq5Dxhm4Tm9n-YYJTfY/edit?tab=t.edzo84ydgghk

Scenarios

1. ...

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment