almalinux
/
pungi
15
1
Fork 0
Code Issues Pull Requests Releases Activity
The utility for building of AlmaLinux distributions (repos, ISO images).
2,471 Commits 3 Branches 355 Tags 8.1 MiB
Python 99.4%
XSLT 0.3%
Shell 0.2%
Makefile 0.1%
Go to file
Christian Kellner 6998ffe694 osbuild: use task result to get build info 
Instead of parsing the log file to get the NVR and then in turn
use that to get to the build info use the structured return value
from the koji task. The return value of the osbuild plugin is:
    result = {
        "composer": {
            "server": <COMPOSER_URL>,
            "id": <COMPOSE_ID>
        },
        "koji": {
            "build": <BUILD_ID>
        }
    }
This means we have direct access to the koji build id, which was
returned by composer to the plugin via its status API. Using that
removes the need to parse the log file.

Adapt the test accordingly.

Merges: https://pagure.io/pungi/pull-request/1475
Signed-off-by: Christian Kellner <christian@kellner.me>
 		2020-11-30 09:57:48 +01:00
contrib/yum-dnf-compare gather: Only parse pungi log once 2017-08-09 11:04:14 +02:00
doc docs: Add osbuild phase to overview diagram 2020-11-27 09:56:10 +01:00
pungi osbuild: use task result to get build info 2020-11-30 09:57:48 +01:00
pungi_utils Support change of the patch-iso temp dir 2020-09-15 15:47:16 +02: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 osbuild: use task result to get build info 2020-11-30 09:57:48 +01:00
.gitignore Run flake8 and black via tox 2020-02-07 16:14:45 +08: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 Use pytest instead of nosetests 2020-07-29 14:57:16 +08: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 git-changelog: Fix running on Python 3 2019-07-02 15:05:25 +02:00
pungi.spec Pungi 4.2.6 release 2020-11-04 12:33:06 +00:00
requirements.txt doc: Update doc/contributing.rst 2020-08-11 20:36:22 +08:00
setup.py Pungi 4.2.6 release 2020-11-04 12:33:06 +00:00
test-requirements.txt Use requirements.txt 2020-08-11 20:36:22 +08:00
tox.ini Use requirements.txt 2020-08-11 20:36:22 +08: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