-
Story
-
Resolution: Unresolved
-
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.
- is blocked by
-
TRT-1983 More granular control over what jobs show up in Component Readiness
-
- In Progress
-
- links to