Implement variables for EPEL minor version management

This introduces a set of variables for managing infrastructure changes
as EPEL minor versions change over time.  This should drastically
simplify our changes during EPEL mass branching.  This also drops the
earlier attempt of EPELCycleNumber and EPELBootstrapNumber variables,
which are no longer used.

Signed-off-by: Carl George <carlwgeorge@gmail.com>
This commit is contained in:
Carl George 2025-08-23 03:37:34 -05:00
commit 79259c6911
8 changed files with 51 additions and 51 deletions

View file

@ -248,29 +248,19 @@ handlers = ["console"]
# Gated bodhi updates
{% for tag in epel_tags %}
[[consumer_config.koji_instances.primary.tags]]
from = "epel10.1-signing-pending"
to = "epel10.1-testing-pending"
key = "{{ (env == 'production')|ternary('epel-10', 'testkey') }}"
keyid = "{{ (env == 'production')|ternary('e37ed158', 'd300e724') }}"
from = "{{ tag }}-signing-pending"
to = "{{ tag }}-testing-pending"
key = "{{ (env == 'production')|ternary('epel-{}'.format(epel_major), 'testkey') }}"
keyid = "{{ (env == 'production')|ternary(epel_key, 'd300e724') }}"
[consumer_config.koji_instances.primary.tags.sidetags]
pattern = 'epel10.1-build-side-<seq_id>'
from = '<sidetag>-signing-pending'
to = '<sidetag>-testing-pending'
trusted_taggers = ['bodhi']
[[consumer_config.koji_instances.primary.tags]]
from = "epel10.0-signing-pending"
to = "epel10.0-testing-pending"
key = "{{ (env == 'production')|ternary('epel-10', 'testkey') }}"
keyid = "{{ (env == 'production')|ternary('e37ed158', 'd300e724') }}"
[consumer_config.koji_instances.primary.tags.sidetags]
pattern = 'epel10.0-build-side-<seq_id>'
pattern = '{{ tag }}-build-side-<seq_id>'
from = '<sidetag>-signing-pending'
to = '<sidetag>-testing-pending'
trusted_taggers = ['bodhi']
{% endfor %}
[[consumer_config.koji_instances.primary.tags]]
from = "epel9-signing-pending"