pungi/pungi
1
2
Fork 6
Code Issues 39 Pull requests 12 Projects Releases Packages Activity Actions
Distribution compose tool
2,899 commits 5 branches 216 tags 23 MiB
  • Python 99%
  • Shell 0.5%
  • XSLT 0.3%
  • Makefile 0.2%
Find a file
Exact
Simon de Vlieger 21f114707c
All checks were successful
Tests / test (pull_request) Successful in 1m57s
Details
Tests / test (push) Successful in 1m55s
Details
boot_iso: fallback global_release and version gen 
We recently deployed the latest pungi to Fedora's compose servers and
started using it to schedule the new `boot_iso` phase with the
`image-builder` backend. After some back and forths to get the
configuration to work we now have builds succeeded [1], [2].

However, these builds do not have their (optional) release field passed
along so we get the default release numbers. This probably isn't
load-bearing but I also don't think it's very pretty; and it's also not
consistent with the other image builds we do.

This commit adjusts the `image-builder` and `kiwi` backends for the
`boot_iso` phase to fallback to the `global_release` field *and* to run
`version_generator` over it, then passes it in the appropriate place for
each Koji task.

[1]: https://koji.fedoraproject.org/koji/taskinfo?taskID=150805175
[2]: https://koji.fedoraproject.org/koji/taskinfo?taskID=150805174

Signed-off-by: Simon de Vlieger <cmdr@supakeen.com>
2026-10-01 10:32:06 +02:00
.forgejo/workflows Switch to Forgejo Actions as CI 2026-07-23 11:29:32 +02:00
contrib OpenShift kubeconfig generation script. 2025-10-31 11:51:19 +01:00
doc Release 4.14.0 2026-08-20 12:04:55 +02:00
pungi boot_iso: fallback global_release and version gen 2026-10-01 10:32:06 +02:00
pungi_utils Black 26.1.0 new format 2026-02-05 17:27:21 +01: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 boot_iso: fallback global_release and version gen 2026-10-01 10:32:06 +02: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
README.md Update documentation links 2026-07-23 11:29:32 +02:00
requirements.txt Drop unused dependencies 2026-08-18 12:53:40 +02:00
setup.cfg Default bztar format for sdist command 2022-12-12 12:10:54 +01:00
setup.py Release 4.14.0 2026-08-20 12:04:55 +02:00
test-requirements.txt Drop parameterized dependency 2025-11-13 12:39:57 +01:00
TODO Drop buildinstall method 2023-10-18 06:38:14 +00:00
tox.ini Drop parameterized dependency 2025-11-13 12:39: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