The utility for building of AlmaLinux distributions (repos, ISO images).
Go to file
Jan Kaluza 2d39490909 Do not add pkgset_koji_builds to modules, but only to pkgset_koji_tag tags.
Also remove the useless listTaggedRPMs call which has been used *only*
to catch the very rare error which happened from time to time when
we used PDC in Pungi few years ago. This rare error is not relevant
anymore now.

Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
2019-03-11 17:56:27 +01:00
bin config: Allow validating configuration in JSON 2019-03-04 14:36:28 +01:00
contrib/yum-dnf-compare gather: Only parse pungi log once 2017-08-09 11:04:14 +02:00
doc 4.1.34 release 2019-03-05 12:37:07 +01:00
pungi Do not add pkgset_koji_builds to modules, but only to pkgset_koji_tag tags. 2019-03-11 17:56:27 +01:00
pungi_utils orchestrator: Log exception to log file 2019-02-27 09:56:29 +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 tests: fix metadata tests when SOURCE_DATE_EPOCH is set 2019-03-09 15:42:57 +01:00
.gitignore Log PDC communications and info for modular composes 2017-10-27 16:20:21 +02: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
GPL Update GPL to latest version from https://www.gnu.org/licenses/gpl-2.0.txt 2015-06-25 07:50:03 -04:00
MANIFEST.in Include all test fixtures in source tarball 2018-10-17 10:09:46 +02:00
Makefile Add script to orchestrate multiple composes 2019-01-08 09:40:36 +01:00
README.md README: add link to documentation 2019-02-18 14:36:48 -07:00
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
git-changelog Use Python 3 print function 2017-08-23 09:41:22 +02:00
pungi.spec 4.1.34 release 2019-03-05 12:37:07 +01:00
setup.py 4.1.34 release 2019-03-05 12:37:07 +01:00
tox.ini Ignore more pycodestyle warnings 2017-06-14 13:21:31 +02: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.