almalinux/pungi
14
1
Fork 0
Code Issues Pull Requests Releases Activity
The utility for building of AlmaLinux distributions (repos, ISO images).
2,711 Commits 3 Branches 366 Tags 9.2 MiB
Python 99.4%
XSLT 0.3%
Shell 0.2%
Makefile 0.1%
0d306d4964
Go to file
Adam Williamson 0d306d4964 Fix 'failable' handling for kiwibuild phase 
The mechanisms here are a bit subtle and the kiwibuild phase
didn't quite get them right. The arg passed to `util.failable`
is supposed to be a boolean, but kiwibuild was passing it the
list of failable arches (which will always evaluate True).

How this is meant to work is that we only make *the Koji task
as a whole* failable (by passing `True` to `util.failable`) if
*all* the arches in it are failable. If *any* arch in the task
is not failable, the task should not be failable.

We allow a subset of arches to fail by passing the Koji task a
list of `optional_arches`, later. If an arch is 'optional', that
arch failing won't cause the Koji task itself to be considered
failed.

This commit fixes the logic (I hope), renames all the variables
and adds a couple of comments to make it clearer what's going on,
and does a bit of making the code simpler.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2024-03-08 15:12:01 -08:00
contrib Add config file for cleaning up cache files 2023-04-12 09:56:43 +08:00
doc Release 4.6.2 2024-03-05 15:01:24 +01:00
pungi Fix 'failable' handling for kiwibuild phase 2024-03-08 15:12:01 -08:00
pungi_utils Drop pungi-orchestrator code 2023-06-02 06:14:10 +00:00
share Allow setting <kojitag/> in <modules/> in variants.xml to get the modules from this Koji tag. 2018-03-21 14:33:45 +01:00
tests Phases/osbuild: support passing 'customizations' for image builds 2024-03-05 14:46:56 +01:00
.gitignore nomacboot option for livemedia koji tasks 2022-03-23 09:36:51 +01:00
AUTHORS extra-files: Write a metadata file enumerating extra files 2016-09-07 13:02:48 +02:00
COPYING Remove FSF address from comments 2016-09-23 10:26:43 +02:00
git-changelog git-changelog: Fix running on Python 3 2019-07-02 15:05:25 +02:00
GPL Update GPL to latest version from https://www.gnu.org/licenses/gpl-2.0.txt 2015-06-25 07:50:03 -04:00
Makefile Use pytest instead of nosetests 2020-07-29 14:57:16 +08:00
MANIFEST.in Default bztar format for sdist command 2022-12-12 12:10:54 +01:00
pungi.spec Release 4.6.2 2024-03-05 15:01:24 +01:00
README.md Correct irc network name & add matrix room 2021-10-25 07:26:18 +00:00
requirements.txt Add support for not having koji volume mounted locally 2023-08-23 07:26:56 +00:00
setup.cfg Default bztar format for sdist command 2022-12-12 12:10:54 +01:00
setup.py Release 4.6.2 2024-03-05 15:01:24 +01:00
test-requirements.txt Make python3-mock dependency optional 2024-01-26 09:45:19 +01:00
TODO Drop buildinstall method 2023-10-18 06:38:14 +00:00
tox.ini Update tox configuration 2024-01-26 09:15:57 +01:00

README.md

Pungi

Pungi is a distribution compose tool.

Composes are release snapshots that contain release deliverables such as:

  • installation trees
    • RPMs
    • repodata
    • comps
  • (bootable) ISOs
  • kickstart trees
    • anaconda images
    • images for PXE boot

Tool overview

Pungi consists of multiple separate executables backed by a common library.

The main entry-point is the pungi-koji script. It loads the compose configuration and kicks off the process. Composing itself is done in phases. Each phase is responsible for generating some artifacts on disk and updating the compose object that is threaded through all the phases.

Pungi itself does not actually do that much. Most of the actual work is delegated to separate executables. Pungi just makes sure that all the commands are invoked in the appropriate order and with correct arguments. It also moves the artifacts to correct locations.

Links