almalinux/pungi
14
1
Fork 0
Code Issues Pull Requests Releases Activity
The utility for building of AlmaLinux distributions (repos, ISO images).
2,536 Commits 3 Branches 366 Tags 9.2 MiB
Python 99.4%
XSLT 0.3%
Shell 0.2%
Makefile 0.1%
195bfbefa4
Go to file
Jan Kaluza 195bfbefa4 Allow specifying $COMPOSE_ID in the repo value for osbs phase. 
There should be an option for `yum_repourls` to point to static
URL, for example when CTS is used. The idea is that instead of
setting `repo` to `AppStream`, we could use link similar to this one:

`https://cts.localhost/api/1/composes/$COMPOSE_ID/repo/?variant=AppStream`

This would be translated to real static link during the OSBS phase:

`https://cts.localhost/api/1/composes/CentOS-Stream-9-20210803.0/repo/?variant=AppStream`

That way this statis link would appear in the yum_repourls.

Merges: https://pagure.io/pungi/pull-request/1543
Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
2021-09-09 10:46:33 +02:00
contrib/yum-dnf-compare gather: Only parse pungi log once 2017-08-09 11:04:14 +02:00
doc Allow specifying $COMPOSE_ID in the repo value for osbs phase. 2021-09-09 10:46:33 +02:00
pungi Allow specifying $COMPOSE_ID in the repo value for osbs phase. 2021-09-09 10:46:33 +02:00
pungi_utils Format code 2021-03-02 18:31:45 +08: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 Allow specifying $COMPOSE_ID in the repo value for osbs phase. 2021-09-09 10:46:33 +02:00
.gitignore Adding multithreading support for pungi/phases/image_checksum.py 2021-08-12 10:13:15 +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
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 Include all test fixtures in source tarball 2018-10-17 10:09:46 +02:00
pungi.spec 4.2.10 release 2021-08-04 17:23:19 +08:00
README.md README: add link to documentation 2019-02-18 14:36:48 -07:00
requirements.txt doc: Update doc/contributing.rst 2020-08-11 20:36:22 +08:00
setup.py 4.2.10 release 2021-08-04 17:23:19 +08:00
test-requirements.txt Use requirements.txt 2020-08-11 20:36:22 +08:00
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
tox.ini Use pytest directly incl. support for posargs, e.g.: 2021-08-12 16:35:47 +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.

Links