Story (Required)

As an OpenShift Builds team member, I want to ensure that there are no Enterprise Contract (EC) violations for each component of OpenShift Builds.

Background (Required)

The recent addition of the Enterprise Contract Policy for openshift-builds aims to ensure that our build and release processes comply with specified standards. Currently, the EC pipelines are failing due to various policy violations across different components. Additionally, the registry-standard EC expects hermetic builds, which conflicts with our need for online builds.

Out of scope

<Defines what is not included in this story>

Approach (Required)

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

Dependencies

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

Acceptance Criteria (Mandatory)

1. EC Violations for each OpenShift Builds component is compiled and documented.
2. Address the identified violations.
3. Enable hermatic build in the tekton build pipelines

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