fedora config files for pungi
4f15d62cdd
The nightly scripts try to send an announcement about compose starting. As this happens before Pungi even started, the compose ID is not known and can not be included in the message. The message about starting rsync sent later will contain the ID correctly. Without the json defined there is a traceback in the cron output, but the errors are not logged anywhere else (but don't actually block anything in the compose process). Relates: https://pagure.io/pungi/issue/698 Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com> |
||
---|---|---|
cloud-nightly.sh | ||
docker-nightly.sh | ||
fedora-atomic.conf | ||
fedora-cloud.conf | ||
fedora-dnf.conf | ||
fedora-docker.conf | ||
fedora-modular.conf | ||
fedora.conf | ||
nightly-dnf.sh | ||
nightly-modular.sh | ||
nightly.sh | ||
README.rst | ||
release-candidate.sh | ||
twoweek-nightly.sh | ||
variants-fedora.xml | ||
variants-modular.xml |
This repo holds the config files that define what goes in and comes out of a Fedora compose using pungi.