We're already building libvirt in the containers already, if we publish
the build in form of, say, RPMs, later stages of the pipeline can
consume the RPMs instead of re-building libvirt from scratch.
Signed-off-by: Erik Skultety <eskultet@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
- meson dist -C build --no-tests
- if test -x /usr/bin/rpmbuild && test "$RPM" != "skip";
then
- rpmbuild --nodeps -ta build/meson-dist/libvirt-*.tar.xz;
+ rpmbuild --clean --nodeps --define "_topdir $PWD/rpmbuild/" -ta build/meson-dist/libvirt-*.tar.xz;
+ mv rpmbuild/RPMS/x86_64/ libvirt-rpms/;
else
meson compile -C build;
meson test -C build --no-suite syntax-check --print-errorlogs;
allow_failure: false
variables:
NAME: centos-stream-8
+ artifacts:
+ expire_in: 1 day
+ paths:
+ - libvirt-rpms
x86_64-centos-stream-9:
allow_failure: false
variables:
NAME: centos-stream-9
+ artifacts:
+ expire_in: 1 day
+ paths:
+ - libvirt-rpms
x86_64-debian-10:
allow_failure: false
variables:
NAME: fedora-34
+ artifacts:
+ expire_in: 1 day
+ paths:
+ - libvirt-rpms
x86_64-fedora-35:
allow_failure: false
variables:
NAME: fedora-35
+ artifacts:
+ expire_in: 1 day
+ paths:
+ - libvirt-rpms
x86_64-fedora-rawhide:
centos-stream-8:
jobs:
- arch: x86_64
+ artifacts:
+ expire_in: 1 day
+ paths:
+ - libvirt-rpms
centos-stream-9:
jobs:
- arch: x86_64
+ artifacts:
+ expire_in: 1 day
+ paths:
+ - libvirt-rpms
+
debian-10:
jobs:
- arch: x86_64
- arch: s390x
allow-failure: true
- fedora-34: x86_64
+ fedora-34:
+ jobs:
+ - arch: x86_64
+ artifacts:
+ expire_in: 1 day
+ paths:
+ - libvirt-rpms
fedora-35:
jobs:
- arch: x86_64
+ artifacts:
+ expire_in: 1 day
+ paths:
+ - libvirt-rpms
- arch: mingw32
allow-failure: true