Story (Required)

As a Red Hat Engineer trying to verify the quality of Builds for OpenShift I want basic CI checks like unit tests to run alongside my build.

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

<Describes the context or background related to this story>

• We have a separate operator for deploying Builds for OpenShift - it has its own logic, and imports Shipwright operator code as a dependency.
• We have Shipwright Build images built on Konflux - one component per image, we have multiple builds per PR "downstream." These are running container builds only.
• Shipwright build has a robust test suite upstream that runs unit tests and an "integration" test with the EnvTest tool.

Out of scope

<Defines what is not included in this story>

• Narrowing set of unit/integration tests running on Konflux PRs with Ginkgo labels. See BUILD-944
• Unit/integration tests for our downstream operator.

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

• Add a step to the Konflux pipeline in our downstream Shipwright/build fork that runs the upstream unit+integration test suite. This should be run for the build controller component only.
• Ensure the task for running unit/integration tests runs after source is cloned and in parallel with the image build process.

Dependencies

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

• Onboard shipwright/build components to Konflux
• Upstream tests

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>

• Shipwright/build unit + integration tests run on downstream PRs
• Build pipelines succeed for pull requests and merged code.
• No documentation, px, or security changes needed.

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