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

Konflux Build Definitions Migration : sbom-json-check-task

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • builds-1.1
    • builds-operator
    • 1
    • False
    • None
    • False
    • Builds Sprint #16

      Story (Required)

      As a Konflux user trying to maintain up-to-date build definitions, I want to remove the deprecated `sbom-json-check` task from the pipelinerun definitions to ensure compatibility with the upcoming changes.

      Background (Required)

      The sbom-json-check task in Konflux build definitions is being deprecated and will be completely removed by Oct'2024. To maintain the validation against Enterprise Contract, users need to migrate their pipelinerun definitions by removing this task entirely.

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      For each identified pipelinerun definition that include the sbom-json-check task:

      a. Remove the sbom-json-check task.

      b. Ensure that Enterprise Contract validation is still maintained.

      Dependencies

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

      Acceptance Criteria (Mandatory)

      1. All instances of the sbom-json-check task are successfully identified in existing pipelinerun definitions
      2. Enterprise Contract validation is maintained after the removal of the sbom-json-check task.

      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
              sabhardw@redhat.com Satyam Bhardwaj
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: