shaba/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-05 13:17:51 +03:00
Code Releases Activity
5d0eeb8cd7
libvirt/ci/manifest.yml

232 lines
4.2 KiB
YAML
Raw Normal View History

gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
projects:
- libvirt
gitlab:
namespace: libvirt
project: libvirt
targets:
ci: Move from 'centos-8' to 'almalinux-8' Upstream lcitool suggests that as a solution to 'centos-8' being removed. Move also the website and other jobs to depend on 'x86_64-almalinux-8-container'. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2022-02-14 19:44:12 +03:00
almalinux-8:
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
jobs:
- arch: x86_64
variables:
RPM: skip
- arch: x86_64
suffix: -clang
variables:
RPM: skip
CC: clang
Add Alpine builds to CI Signed-off-by: Martin Kletzander <mkletzan@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-03-15 12:26:46 +03:00
alpine-314:
jobs:
- arch: x86_64
alpine-edge:
jobs:
- arch: x86_64
allow-failure: true
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
centos-stream-8:
jobs:
- arch: x86_64
ci: manifest: Publish RPMs as artifacts on CentOS Stream and Fedoras 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>
2021-10-05 12:01:34 +03:00
artifacts:
expire_in: 1 day
paths:
- libvirt-rpms
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
ci: containers: Add CentOS Stream 9 target Signed-off-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2022-01-27 14:46:32 +03:00
centos-stream-9:
jobs:
- arch: x86_64
ci: manifest: Publish RPMs as artifacts on CentOS Stream and Fedoras 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>
2021-10-05 12:01:34 +03:00
artifacts:
expire_in: 1 day
paths:
- libvirt-rpms
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
debian-10:
jobs:
- arch: x86_64
- arch: aarch64
allow-failure: true
builds: false
- arch: armv6l
- arch: armv7l
ci: Add Debian 11 builds The armv7l and ppc64le cross-builds as well as the Clang build are adopted from Debian 10, while the mips64el build is adopted from Debian sid. As always, the way jobs are distributed across Debian versions is fairly arbitrary. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2021-09-10 17:48:25 +03:00
allow-failure: true
builds: false
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
- arch: i686
allow-failure: true
builds: false
- arch: mips
- arch: mips64el
allow-failure: true
builds: false
- arch: mipsel
ci: Add Debian 11 builds The armv7l and ppc64le cross-builds as well as the Clang build are adopted from Debian 10, while the mips64el build is adopted from Debian sid. As always, the way jobs are distributed across Debian versions is fairly arbitrary. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2021-09-10 17:48:25 +03:00
- arch: ppc64le
allow-failure: true
builds: false
- arch: s390x
allow-failure: true
builds: false
debian-11:
jobs:
- arch: x86_64
- arch: x86_64
suffix: -clang
- arch: aarch64
allow-failure: true
builds: false
- arch: armv6l
allow-failure: true
builds: false
- arch: armv7l
- arch: i686
allow-failure: true
builds: false
- arch: mips64el
- arch: mipsel
allow-failure: true
builds: false
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
- arch: ppc64le
- arch: s390x
allow-failure: true
builds: false
debian-sid:
jobs:
- arch: x86_64
ci: switch all non-released distros to be non-gating The non-released distros have reasonably frequent package installation failures that can last for days at a time. This makes them unsuitable for use as gating CI jobs. This ensures all of the jobs in Debian Sid, Fedora Rawhide, openSUSE Tumbleweed and FreeBSD Current are marked "allow-failure: true". This means the jobs still run, but any failure will not be considered fatal to the pipeline. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-10-20 13:43:37 +03:00
allow-failure: true
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
- arch: aarch64
ci: switch all non-released distros to be non-gating The non-released distros have reasonably frequent package installation failures that can last for days at a time. This makes them unsuitable for use as gating CI jobs. This ensures all of the jobs in Debian Sid, Fedora Rawhide, openSUSE Tumbleweed and FreeBSD Current are marked "allow-failure: true". This means the jobs still run, but any failure will not be considered fatal to the pipeline. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-10-20 13:43:37 +03:00
allow-failure: true
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
- arch: armv6l
allow-failure: true
builds: false
- arch: armv7l
allow-failure: true
builds: false
- arch: i686
ci: switch all non-released distros to be non-gating The non-released distros have reasonably frequent package installation failures that can last for days at a time. This makes them unsuitable for use as gating CI jobs. This ensures all of the jobs in Debian Sid, Fedora Rawhide, openSUSE Tumbleweed and FreeBSD Current are marked "allow-failure: true". This means the jobs still run, but any failure will not be considered fatal to the pipeline. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-10-20 13:43:37 +03:00
allow-failure: true
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
- arch: mips64el
ci: Add Debian 11 builds The armv7l and ppc64le cross-builds as well as the Clang build are adopted from Debian 10, while the mips64el build is adopted from Debian sid. As always, the way jobs are distributed across Debian versions is fairly arbitrary. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2021-09-10 17:48:25 +03:00
allow-failure: true
builds: false
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
- arch: mipsel
allow-failure: true
builds: false
- arch: ppc64le
allow-failure: true
builds: false
- arch: s390x
ci: switch all non-released distros to be non-gating The non-released distros have reasonably frequent package installation failures that can last for days at a time. This makes them unsuitable for use as gating CI jobs. This ensures all of the jobs in Debian Sid, Fedora Rawhide, openSUSE Tumbleweed and FreeBSD Current are marked "allow-failure: true". This means the jobs still run, but any failure will not be considered fatal to the pipeline. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-10-20 13:43:37 +03:00
allow-failure: true
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
ci: manifest: Publish RPMs as artifacts on CentOS Stream and Fedoras 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>
2021-10-05 12:01:34 +03:00
fedora-34:
jobs:
- arch: x86_64
artifacts:
expire_in: 1 day
paths:
- libvirt-rpms
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
ci: run a mingw64 job on stable Fedora Both of the current mingw jobs are marked as 'allow_failure' because they are running against Fedora rawhide which is an unstable distro. We need at least one mingw job to be gating to more reliably detect problems. This introduces dockerfiles for both mingw variants on Fedora 35 and sets the mingw64 build to run on Fedora 34, and mingw32 on Fedora rawhide. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-11-23 15:12:25 +03:00
fedora-35:
jobs:
- arch: x86_64
ci: manifest: Publish RPMs as artifacts on CentOS Stream and Fedoras 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>
2021-10-05 12:01:34 +03:00
artifacts:
expire_in: 1 day
paths:
- libvirt-rpms
ci: run a mingw64 job on stable Fedora Both of the current mingw jobs are marked as 'allow_failure' because they are running against Fedora rawhide which is an unstable distro. We need at least one mingw job to be gating to more reliably detect problems. This introduces dockerfiles for both mingw variants on Fedora 35 and sets the mingw64 build to run on Fedora 34, and mingw32 on Fedora rawhide. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-11-23 15:12:25 +03:00
- arch: mingw32
allow-failure: true
builds: false
- arch: mingw64
ci: replace Fedora 33 with Fedora 35 Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-11-23 15:09:00 +03:00
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
fedora-rawhide:
jobs:
- arch: x86_64
allow-failure: true
- arch: x86_64
suffix: -clang
allow-failure: true
variables:
CC: clang
RPM: skip
- arch: mingw32
allow-failure: true
- arch: mingw64
allow-failure: true
ci: run a mingw64 job on stable Fedora Both of the current mingw jobs are marked as 'allow_failure' because they are running against Fedora rawhide which is an unstable distro. We need at least one mingw job to be gating to more reliably detect problems. This introduces dockerfiles for both mingw variants on Fedora 35 and sets the mingw64 build to run on Fedora 34, and mingw32 on Fedora rawhide. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-11-23 15:12:25 +03:00
builds: false
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
freebsd-12: x86_64
freebsd-13: x86_64
freebsd-current:
jobs:
- arch: x86_64
ci: switch all non-released distros to be non-gating The non-released distros have reasonably frequent package installation failures that can last for days at a time. This makes them unsuitable for use as gating CI jobs. This ensures all of the jobs in Debian Sid, Fedora Rawhide, openSUSE Tumbleweed and FreeBSD Current are marked "allow-failure: true". This means the jobs still run, but any failure will not be considered fatal to the pipeline. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-10-20 13:43:37 +03:00
allow-failure: true
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
builds: False
opensuse-leap-152:
jobs:
- arch: x86_64
variables:
RPM: skip
opensuse-tumbleweed:
jobs:
- arch: x86_64
ci: switch all non-released distros to be non-gating The non-released distros have reasonably frequent package installation failures that can last for days at a time. This makes them unsuitable for use as gating CI jobs. This ensures all of the jobs in Debian Sid, Fedora Rawhide, openSUSE Tumbleweed and FreeBSD Current are marked "allow-failure: true". This means the jobs still run, but any failure will not be considered fatal to the pipeline. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-10-20 13:43:37 +03:00
allow-failure: true
gitlab: define a manifest file to express the CI config Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-25 15:05:41 +03:00
variables:
RPM: skip
macos-11:
jobs:
- arch: x86_64
variables:
PATH_EXTRA: /usr/local/opt/ccache/libexec:/usr/local/opt/gettext/bin:/usr/local/opt/libpcap/bin:/usr/local/opt/libxslt/bin:/usr/local/opt/rpcgen/bin
PKG_CONFIG_PATH: /usr/local/opt/curl/lib/pkgconfig:/usr/local/opt/libpcap/lib/pkgconfig:/usr/local/opt/libxml2/lib/pkgconfig:/usr/local/opt/ncurses/lib/pkgconfig:/usr/local/opt/readline/lib/pkgconfig
ubuntu-2004:
jobs:
- arch: x86_64
variables:
ASAN_OPTIONS: verify_asan_link_order=0
MESON_ARGS: -Db_lundef=false -Db_sanitize=address,undefined
UBSAN_OPTIONS: print_stacktrace=1:halt_on_error=1
- arch: x86_64
suffix: -clang
variables:
CC: clang
MESON_ARGS: -Db_lundef=false -Db_sanitize=address,undefined
UBSAN_OPTIONS: print_stacktrace=1:halt_on_error=1
Copy Permalink