The tier1 tests were traditionally run by BaseOS CI by various
tasks if the baseos-ci.brew-build.* family, typically implemented
by Beaker jobs.
Every component used to have its own special flavor of the
configuration, both in BaseOS CI (the triggering part) and here in
the component's gating.yaml (results processing).
The each-component-is-a-snowflake approach didn't work very well,
creating discrepancies like RHEL-140879.
At long last, I've unified the BaseOS CI configuration for all my
components:
- drop the Beaker job(s) (which have been declared obsoleted anyway)
- trigger two OpenStack jobs
- "fast lane" for architectures where we usually get results fast,
sometimes it's advantageous to take a look ASAP
- "slow lane" for architectures we typically have to wait
For reference, it's commit d2baef686 in baseos-qe/citool-config.
Now I'm fixing the counterpart in gating.yaml (results processing):
We wait for the "fast lane" and "slow lane" results and they both
must pass.
- Bring the same rpminspect configuration we already have in older
RHELs. We'll need it.
- Inject component=gcc-toolset-15-gcc as a new context item into tmt
testing. The reason:
On the old times ("SCL" times) we were able to recognize
GCC Toolset builds and adjust individual test thanks to mere
existence of the "collection=gcc-toolset-<NN>" item in the context.
For SCL-less GCC Toolsets it's no longer possible. Therefore we
need:
- inject the new context item here (and all other downstream plans
which is however out of scope of this commit)
- update the metadata in all the downstream tests that adjust
themselves depending on the "collection" item in the context
(this again is out of scope here)
This should be an equivalent to what system GCC of CentOS Stream 10
already has [1].
Because gcc-toolset-15-gcc will be scl-less and I have no prototype
to work with, let's take this as a first draft for now. Definitely
using the WITH_SCL variable is confusing and an obvious candidate
for an improvement...
Related: RHEL-92605
[1] 5780c4d2e3
