Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-1131

Fix Enterprise Contract Violations : outdated exceptions in the EC Policy

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • builds-1.2
    • builds-1.1
    • builds-operator
    • None
    • 2
    • False
    • None
    • False
    • Builds Sprint #15, Builds Sprint #16
    • 2

      Story (Required)

      As an OpenShift Builds developer, I want to resolve the Enterprise Contract violations caused by outdated exceptions in the EC Policy.

      Background (Required)

      Several exceptions in the Enterprise Contract Policy for OpenShift Builds are no longer applicable. These exceptions were temporary measures to allow the team time to release Builds 1.1 on time.
      The list of exceptions are here - https://gitlab.cee.redhat.com/releng/konflux-release-data/-/blob/main/config/stone-prd-rh01.pg1f.p1/product/EnterpriseContractPolicy/registry-rh-openshift-builds.yaml#L17-34

      Note: More sub-tasks might be needed depending on the outcome from another assessment of the violations.

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      1. For each exception, develop a plan to update the PipelineRun definitions to comply with the EC Policy.

      2. Modifying the Enterprise Contract Policy to ensure only applicable exceptions are there.

      Dependencies

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

      Acceptance Criteria (Mandatory)

      1. Updated PipelineRun definitions pass EC validation without any violations.

      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

              sabhardw@redhat.com Satyam Bhardwaj (Inactive)
              sabhardw@redhat.com Satyam Bhardwaj (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: