This adds pruning for atomic workstation. We don't yet rsync atomic
workstation out like we do for atomic host. I'm not sure why but didn't
want to add that as part of this commit.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
This will enable the optimizations landed in
https://github.com/rhinstaller/anaconda/pull/1119
to avoid lots of HTTP requests when installing the cloud images.
Signed-off-by: Colin Walters <walters@verbum.org>
Instead of having to add the `--treename` argument after each branching,
let the script compute it automatically.
Relates: https://pagure.io/pungi-fedora/issue/350
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
Creating the image requires running lorax. There is however already one
lorax instance being run in the buildinstall phase. When the second one
runs, it overwrites the outputs from first one and people expecting to
boot netinst over PXE are instead getting ostree workstation.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1477916
Relates: https://pagure.io/pungi/issue/695
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
Since not all builds are signed with f28 key yet, we will use f27 key
also and once everything is signed with f28 then we will remove f27 key
Signed-off-by: Mohan Boddu <mboddu@redhat.com>
composes were failing because the 2nd image build task
for the minimal image (copied from fedora.conf) didn't
have some variables defined. In fedora.conf the global_*
vars are defined, so let's do that here too.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
We don't create a repo during this pungi run. We need to pull
from a repo that was already created.
This was a copy/paste error from f6e7f69.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
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>
Since we are currently building atomic host media every night using
the cloud variant then we need to add ostree-support group if we
want to pull in new ostree tools into the ISO installer images.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
It's failing on ppc64le, we're at 87% on x86_64. There's really no reason not to
bump this to give ourselves some room at least on 64 bit architectures.
Signed-off-by: Colin Walters <walters@verbum.org>
The script gets a label as a command line argument, and this is manually
handled by adding it as `--label=$1` to the pungi-koji command. We
should not add this argument to another time.
This avoid problem with Pungi 4.1.17 which reports an error when seeing
unknown arguments (which were silently ignored before).
Fixes: https://pagure.io/pungi/issue/682
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
Currently the l10n support is moved to a single calligra-l10n package
(which is a subpackage of calligra itself) as opposed to previously
separate calligra-l10n package with a separate subpackage for each
language (which is now retired).
Due `greedy_method = "build"` the l10n subpackage will be pulled into
the compose if some package from the same build gets in (i.e. the main
calligra package required by comps).
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
Since we pull from ostree repos it doesn't really make
sense to provide a yum "repo" to the image build in pungi.
Removing it since it could be confusing to have it there.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
