Compare commits

..

1 Commits
c8 ... c8s

Author SHA1 Message Date
Václav Kadlčík
bcdf2bcb42 Standardize tier1 in gating
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.
2026-02-13 14:33:35 +01:00
8 changed files with 52 additions and 2 deletions

1
.fmf/version Normal file
View File

@ -0,0 +1 @@
1

View File

@ -1 +0,0 @@
16f4ce654c97226c3046fabc1ef9cf21d014ad4d SOURCES/dwz-0.16.tar.xz

2
.gitignore vendored
View File

@ -1 +1 @@
SOURCES/dwz-0.16.tar.xz
/dwz-0.16.tar.xz

7
gating.yaml Normal file
View File

@ -0,0 +1,7 @@
--- !Policy
product_versions:
- rhel-8
decision_context: osci_compose_gate
rules:
- !PassingTestCaseRule {test_case_name: baseos-ci.brew-build.gate-build-fast-lane.functional}
- !PassingTestCaseRule {test_case_name: baseos-ci.brew-build.gate-build-slow-lane.functional}

32
plans/tier0.fmf Normal file
View File

@ -0,0 +1,32 @@
# Tier 0 test plan. It's actually Tier 1
# - limited to its public part
# - executed on the architecture at hand
# When run by osci.tier0 on CentOS Stream or RHEL, it receives the following
# context:
# arch=x86_64 (the architecture at hand, currently OSCI uses just x86_64)
# distro=rhel<M>.<m> (even for CentOS Stream builds)
# trigger=build
summary: Tier 0 test plan
context:
component: gcc-toolset-15-dwz
discover:
- name: collect_info
how: shell
tests:
- name: /info/rpms
test: rpm -qa --last
- name: public_tests
how: fmf
url: https://gitlab.com/redhat/centos-stream/tests/dwz.git
filter: tier:1
execute:
how: tmt
prepare+:
how: shell
script:
- dnf config-manager --set-enabled '*CRB*' || true
- dnf config-manager --set-enabled crb || true
environment+:
COLLECTIONS: gcc-toolset-15
WITH_SCL: "scl enable gcc-toolset-15"

10
rpminspect.yaml Normal file
View File

@ -0,0 +1,10 @@
runpath:
allowed_paths:
- /usr/lib64
specname:
# In GCC toolsets builds, the spec file name and the package are not
# exactly the same, the package is prefixed with gcc-toolset-NN-.
# Let's ignore the prefix in the specname test.
match: suffix
primary: filename

1
sources Normal file
View File

@ -0,0 +1 @@
SHA512 (dwz-0.16.tar.xz) = 1d6584ad8a0558b8a1351472c968c7b86849267872a50f11ab7b2a0866403dfb2dcf5e14c7c1a97a7c014c7b9fe8ce56c37aaa28b04bd6ddb0fd04bfbc8b97fe