Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-1607

Declare OCL an OCP variant

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • MCO Sprint 274
    • 0
    • 0

      Within the context Sippy and OpenShift CI, the term "variant" has numerous connotations. For example, single-node is considered an OCP variant, as is disconnected, etc. The intent is to ensure that trends amongst variants can be identified independently of one another and job failure rates can be examined intrinsically as well as holistically.

      And even within OCL, I see there being a few sub-variants such as:

      • External image registry
      • Internal image registry

       

      Done When:

      • Any testing jobs which target OCL (such as the ones defined in MCO-1606) have been updated to indicate that they are part of the OCL variant.
      • Sippy's Variant Registry has been updated accordingly. This will likely require a TRT consultation since, as of this writing, none of their variant keys seem like a natural fit for OCL.
      • It's been verified that the jobs are being classified as an OCL variant.

              dkhater@redhat.com Dalia Khater
              zzlotnik@redhat.com Zack Zlotnik
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: