jialiu@redhat.com is a contributor for unified quality signal across Eng &QE in component readiness. This work lines up well with his TRT rotation and we want to leverage that time to define a plan around this initiative and work on these goals

Initial questions to help layout a plan for moving forward are listed below

QE's periodical ci jobs are located in https://github.com/openshift/release/tree/master/ci-operator/config/openshift/openshift-tests-private

We need to get know about the requirements, e.g:

• Current the QE's ci job results are saved in a private gcs deck, it has to be public, right?
  • stbenjam has moved openshift private util to ote - Let's review next steps
• What is the ideal time duration to run the ci jobs ?
  • I believe our longest currently running jobs are around 6 hours but we might want to target 4.
• Should we create a new repo, and migrate the jobs one by one, set them to a proper job tier in order to not break the default CR, keep watching and refining the pass ratio and stability?
  • Is there anything under openshift that already exists?
• Is there a basic requirement for e2e pass ratio for these jobs?
  • Release gating discusses stability and pass ratio, in general a 70% pass rate is required for informing jobs
• When pass ratio and stability is met, shall we promote the job tier to make them show in the default CR review?

The goal of this card is to review with stbenjam and team to outline implementation steps to work toward the goal of unifying QE and Eng signal in CR.