shaba/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-01-21 22:03:49 +03:00
Code Releases Activity
libvirt/ci/manifest.yml

231 lines
4.4 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 12:05:41 +00:00
projects:
- libvirt
gitlab:
namespace: libvirt
project: libvirt
targets:
ci: Switch from AlmaLinux 8 to AlmaLinux 9 By the time of release, it's going to be more than two years since AlmaLinux 9 was released and per our support policy, AlmaLinux 8 (the previous major release) will be not supported. Switch from AlmaLinux 8 to AlmaLinux 9. This also means the website_job which depends on AlmaLinux 8 needs to be moved to newer AlmaLinux. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2024-05-03 19:52:58 +02:00
almalinux-9:
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 12:05:41 +00:00
jobs:
- arch: x86_64
ci: disable native builds on certain distros Currently we do native builds on all distros that are covered by the support matrix. This reduces that such that we mostly only run builds on the newest (ie bleeding edge non-released) version and the oldest version. The effect is that cut out builds on the newest release version. This is acceptable, because that version is sandwiched between two versions we do still test, so unlikely to have failures not already identified by other jobs. This has the effect of disabling: - AlmaLinux 8 GCC - still has a CLang build and CentOS 8 Stream also gives coverage - Debian 11 - still has a Debian 10 and Sid build - Alpine 3.15 - still has a Alpine 3.14 and Edge build Ideally Fedora 35 would be disabled too, but we rely on that for the integration tests. The Ubuntu jobs will be handled in the next patch. The containers are still built since this is cheap-ish. The build jobs can also be triggered manually if desired. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:18 -04: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 12:05:41 +00:00
variables:
RPM: skip
- arch: x86_64
suffix: -clang
variables:
RPM: skip
CC: clang
ci: Update Alpine and Fedora and regenerate New Alpine and Fedora releases were added to libvirt-ci (3.19 and 39, respectively) and old ones were removed. Update the manifest file and regenerate the rest. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com>
2023-12-14 08:36:01 +01:00
alpine-319: x86_64
ci: Add Alpine Linux 3.15 It was released in November 2021. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Martin Kletzander <mkletzan@redhat.com>
2022-04-12 18:59:40 +02:00
Add Alpine builds to CI Signed-off-by: Martin Kletzander <mkletzan@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-03-15 10:26:46 +01:00
alpine-edge:
jobs:
- arch: x86_64
allow-failure: true
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 12:46:32 +01: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 11:01:34 +02:00
artifacts:
expire_in: 1 day
paths:
- libvirt-rpms
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 16:48:25 +02:00
debian-11:
jobs:
- arch: x86_64
ci: Move Debian-11 workloads to Debian-12 Let's move our Debian CI workloads to Debian-12 since it's the latest release and mark Debian-11 jobs as optional. Signed-off-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2023-08-11 11:46:20 +02:00
builds: false
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 16:48:25 +02:00
- arch: x86_64
suffix: -clang
ci: Move Debian-11 workloads to Debian-12 Let's move our Debian CI workloads to Debian-12 since it's the latest release and mark Debian-11 jobs as optional. Signed-off-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2023-08-11 11:46:20 +02:00
builds: false
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 16:48:25 +02:00
- arch: aarch64
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: false
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 16:48:25 +02:00
builds: false
- arch: armv6l
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: false
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 16:48:25 +02:00
builds: false
- arch: armv7l
ci: Move Debian-11 workloads to Debian-12 Let's move our Debian CI workloads to Debian-12 since it's the latest release and mark Debian-11 jobs as optional. Signed-off-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2023-08-11 11:46:20 +02:00
builds: false
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 16:48:25 +02:00
- arch: i686
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: false
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 16:48:25 +02:00
builds: false
- arch: mips64el
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: false
builds: false
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 16:48:25 +02:00
- arch: mipsel
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: false
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 16:48:25 +02: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 12:05:41 +00:00
- arch: ppc64le
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: false
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 12:05:41 +00:00
- arch: s390x
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: 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 12:05:41 +00:00
builds: false
ci: Move Debian-11 workloads to Debian-12 Let's move our Debian CI workloads to Debian-12 since it's the latest release and mark Debian-11 jobs as optional. Signed-off-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2023-08-11 11:46:20 +02:00
debian-12:
jobs:
- arch: x86_64
- arch: x86_64
suffix: -clang
- arch: aarch64
containers: false
builds: false
- arch: armv6l
containers: false
builds: false
- arch: armv7l
- arch: i686
containers: false
builds: false
- arch: mips64el
containers: false
builds: false
- arch: mipsel
containers: false
builds: false
- arch: ppc64le
containers: false
builds: false
- arch: s390x
containers: false
builds: false
ci: Add Debian-12 target Signed-off-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2023-08-11 11:37:46 +02: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 12:05:41 +00:00
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 11:43:37 +01: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 12:05:41 +00:00
- arch: aarch64
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: false
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 12:05:41 +00:00
- arch: armv6l
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: 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 12:05:41 +00:00
builds: false
- arch: armv7l
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: 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 12:05:41 +00:00
builds: false
- arch: i686
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: false
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 12:05:41 +00:00
- arch: mips64el
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: false
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 16:48:25 +02: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 12:05:41 +00:00
- arch: ppc64le
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: 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 12:05:41 +00:00
builds: false
- arch: s390x
ci: eliminate many cross arch CI builds We currently build cross-arch containers for all three Debian releases (10, 11, Sid), and do libvirt builds covering each arch. This is overkill in terms of the number of problems it identifies. The most important aspect of cross arch builds is to find problems with 32-bit builds and problems with big endian builds. With this in mind the cross arch jobs are altered as follows - Debian 10 - build the containers by default - build armv7 (32-bit) & s390x (big endian) - other arch builds manual - Debian 11 / Sid - container builds all optional - arch builds all optional Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:20 -04:00
containers: false
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 12:05:41 +00:00
ci: Switch from Fedora 38 to Fedora 40 Since Fedora 40 was released recently, Fedora 38 is now unsupported. Drop Fedora 38 and introduce Fedora 40 to our CI. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2024-05-03 19:48:28 +02:00
fedora-39:
ci: Move MinGW jobs to Fedora 36 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-26 08:39:10 +02:00
jobs:
- arch: x86_64
ci: Add Fedora 36 to integration tests This requires publishing the RPMs as artifacts from the regular build job. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-26 15:43:36 +02:00
artifacts:
expire_in: 1 day
paths:
- libvirt-rpms
ci: Move MinGW jobs to Fedora 36 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-26 08:39:10 +02:00
ci: Switch from Fedora 38 to Fedora 40 Since Fedora 40 was released recently, Fedora 38 is now unsupported. Drop Fedora 38 and introduce Fedora 40 to our CI. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2024-05-03 19:48:28 +02:00
fedora-40:
ci: Add Fedora 38 target Signed-off-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com>
2023-05-02 17:08:21 +02:00
jobs:
- arch: x86_64
artifacts:
expire_in: 1 day
paths:
- libvirt-rpms
ci: Switch from Fedora 38 to Fedora 40 Since Fedora 40 was released recently, Fedora 38 is now unsupported. Drop Fedora 38 and introduce Fedora 40 to our CI. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2024-05-03 19:48:28 +02:00
- arch: mingw32
builds: false
- arch: mingw64
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 12:05:41 +00: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 12:12:25 +00: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 12:05:41 +00:00
freebsd-13: x86_64
ci: Switch from FreeBSD 12.0 to FreeBSD 14.0 FreeBSD 12.0 is no longer supported since 14.0 is out. Change the CI manifest and refresh the rest. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2024-01-03 10:07:49 +01:00
freebsd-14: x86_64
ci: Regenerate files This removes minor version number from OpenSUSE LEAP target names and on CentOS Stream 9 installs flake8 from repositories, instead of pip. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Pavel Hrdina <phrdina@redhat.com>
2023-04-27 08:48:21 +02:00
opensuse-leap-15:
ci: Add OpenSUSE leap 15.4 job As a precursor to dropping the EOL OpenSUSE 15.3 job add first the definitions for the replacement version. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2023-03-23 15:21:37 +01:00
jobs:
- arch: x86_64
variables:
RPM: skip
ci: workaround broken opensuse leap 15.5 tirpc Temporarily disable '-Wmissing-include-dirs' becuase the libtirpc pkg-config file has a bogus include dir. The headers can fortunately still be found since they are in the system include dir. Reviewed-by: Martin Kletzander <mkletzan@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2023-11-03 09:22:42 -04:00
# Keep until fix for: https://bugzilla.opensuse.org/show_bug.cgi?id=1216862
CFLAGS: -Wno-missing-include-dirs
ci: Add OpenSUSE leap 15.4 job As a precursor to dropping the EOL OpenSUSE 15.3 job add first the definitions for the replacement version. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2023-03-23 15:21:37 +01: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 12:05:41 +00:00
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 11:43:37 +01: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 12:05:41 +00:00
variables:
RPM: skip
ci: Add macOS 13 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2023-11-06 11:35:40 +01:00
macos-13:
jobs:
- arch: aarch64
variables:
PATH_EXTRA: /usr/local/opt/ccache/libexec:/usr/local/opt/gettext/bin:/usr/local/opt/libpcap/bin:/usr/local/opt/libxslt/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
ci: Add macOS 14 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2023-11-06 11:36:15 +01:00
macos-14:
jobs:
- arch: aarch64
variables:
PATH_EXTRA: /usr/local/opt/ccache/libexec:/usr/local/opt/gettext/bin:/usr/local/opt/libpcap/bin:/usr/local/opt/libxslt/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
ci: move Ubuntu GCC santizers build to 20.04 We currently build on Ubuntu 22.04 twice, for GCC and CLang with santizers turned on. Moving the GCC santizers build to 20.04 lets us cull one of the 22.04 jobs Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-05-27 10:06:19 -04:00
ubuntu-2204:
jobs:
- arch: x86_64
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 12:05:41 +00:00
- 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