fedora config files for pungi
Go to file
Jan Kaluza 594715e0a7 ELN: Wait for 60 * 20 seconds (20 minutes) for packages to sign.
Sometimes the compose is when builds are tagging in the Koji tag
but are not signed yet. The automation which signs them need some
time to do so.

In this commit, we wait up to 20 minutes for the signing to happen.

Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
2021-02-22 09:04:51 +01:00
fedora ELN: Add F35 signing key. 2021-02-17 18:30:41 +01:00
shared ELN: Wait for 60 * 20 seconds (20 minutes) for packages to sign. 2021-02-22 09:04:51 +01:00
content-resolver-to-gather-source-json
eln.conf
prepopulate.json
README.rst
variants.xml

This repository holds the config files that define Fedora ELN compose, 
Future CentOS Stream compose and Future RHEL compose.

The repository is organized into several directories:

- ``shared`` - Pungi configuration files defining compose options
  which are shared between all Fedora ELN, CentOS Stream and RHEL.
  There is one Pungi configuration file for each Pungi phase and
  also ``general.conf``, ``multilib.conf`` and
  ``additional_and_filter_packages.conf`` defining compose options
  which are not specific for any particular phase.
- ``fedora`` - Pungi configuration files which extend the ``shared``
  compose options (and in some cases overrides them) for Fedora ELN
  compose.
- ``centos`` - Pungi configuration files which extend the ``shared``
  compose options (and in some cases overrides them) for CentOS
  compose.
- ``rhel`` - Pungi configuration files which extend the ``shared``
  compose options (and in some cases overrides them) for RHEL
  compose.

In the main directory, there is one file for each compose which can
be generated from thie configuration files repository. Each config
file imports the ``shared`` configuration files and also the ``fedora``,
``centos`` or ``rhel`` specific overrides.

Compose variants (repositories)
###############################

So far the compose repositories are defined by the Content Resolver.
There is a ``content-resolver-to-gather-source-json`` Python script
which queries the Content Resolver API and generated ``gather_source.json``
which defines which RPM is in which Compose variant.

In the future this will be replaced by comps files, but these are not
defined yet.