Uploaded image for project: 'OCP Technical Release Team'
  1. OCP Technical Release Team
  2. TRT-1922

Component readiness and classic Sippy should sync the same jobs

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • False
    • None
    • False

      Are we able to get rid of sippy-config-generator (https://github.com/openshift/ci-tools/blob/master/cmd/sippy-config-generator/main.go) and make classic sippy and Component Readiness always sync the same jobs?

      There's a new JobTier which I think we can leverage to selectively filter what ends up in Sippy, by creating an "excluded" tier that we default to.

              stbenjam Stephen Benjamin
              stbenjam Stephen Benjamin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: