The utility for building of AlmaLinux distributions (repos, ISO images).
5b6e468952
`pungi-gather` (the tool that underlies both the `pkgset` and `gather` phases) contains profiling code that will log statistics about how long different function calls take. However, pungi-koji did not contain a way to pass the ``--profiler`` argument to enable this. This change adds a new configuration option ``gather_profiler`` which, when set to true, simply passes the argument to `pungi-koji`. Hopefully this can help shed some light on what is happening in some of our longer-running composes. Merges: https://pagure.io/pungi/pull-request/727 Signed-off-by: Ralph Bean <rbean@redhat.com> |
||
---|---|---|
bin | ||
contrib/yum-dnf-compare | ||
doc | ||
pungi | ||
pungi_utils | ||
share | ||
tests | ||
.gitignore | ||
AUTHORS | ||
COPYING | ||
git-changelog | ||
GPL | ||
Makefile | ||
MANIFEST.in | ||
pungi.spec | ||
README.md | ||
RELEASE-NOTES | ||
setup.py | ||
TODO | ||
tox.ini |
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
- Upstream GIT: https://pagure.io/pungi/
- Issue tracker: https://pagure.io/pungi/issues
- Questions can be asked on #fedora-releng IRC channel on FreeNode