Epic Goal

Provide a more robust and automated CI experience in downstream "builds for OpenShift" so that we can release with confidence. Testing will focus on the product itself, as it would be deployed on OpenShift.

Why is this important?

• Downstream/"midstream" - ensure the builds for OpenShift operator works on OpenShift (ideally pre-merge).
• Downstream - automate build of operator and trigger tests on CPaaS.
• Downstream - automate e2e tests against all versions of OCP we support.

Scenarios

1. Bump version of shipwright-io/build and other components
2. Facilitate testing of z-streams

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. BUILD-780: this focused on upstream quality improvements.

Open questions:

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