External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-11-05 04:41:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
5a42a8c38c
libvirt/ci/manifest.yml

202 lines
3.7 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: 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 16:44:12 +00: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 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 14:06:18 +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
variables:
RPM: skip
- arch: x86_64
suffix: -clang
variables:
RPM: skip
CC: clang
ci: Move builds from alpine-314 to alpine-315 'lcitool' dropped alpine-314 Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com>
2022-07-22 10:19:53 +00:00
alpine-315: 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 16:59:40 +00:00
Add Alpine builds to CI Signed-off-by: Martin Kletzander <mkletzan@redhat.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2022-03-15 09:26:46 +00:00
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 12:05:41 +00: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 09:01:34 +00: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 12:05:41 +00: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 11:46:32 +00: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 09:01:34 +00: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 14:48:25 +00:00
debian-11:
jobs:
- arch: x86_64
- arch: x86_64
suffix: -clang
- 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 14:06:20 +00: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 14:48:25 +00: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 14:06:20 +00: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 14:48:25 +00:00
builds: false
- arch: armv7l
- 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 14:06:20 +00: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 14:48:25 +00: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 14:06:20 +00: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 14:48:25 +00: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 14:06:20 +00: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 14:48: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
- 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 14:06:20 +00: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 14:06:20 +00: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
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 10:43:37 +00: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 14:06:20 +00: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 14:06:20 +00: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 14:06:20 +00: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 14:06:20 +00: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 14:06:20 +00: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 14:48: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
- 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 14:06:20 +00: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: 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 14:06:20 +00: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 14:06:20 +00: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: Refresh and add Fedora 37 target Signed-off-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Martin Kletzander <mkletzan@redhat.com>
2023-01-04 09:12:42 +00:00
fedora-36:
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
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 09:01:34 +00: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 12:12:25 +00:00
ci: Refresh and add Fedora 37 target Signed-off-by: Erik Skultety <eskultet@redhat.com> Reviewed-by: Martin Kletzander <mkletzan@redhat.com>
2023-01-04 09:12:42 +00:00
fedora-37:
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 06:39:10 +00: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 13:43:36 +00: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 06:39:10 +00: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 12:12:25 +00:00
- arch: mingw32
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 12:09:00 +00: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
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-12: x86_64
freebsd-13: x86_64
ci: Add openSUSE Leap 15.3 It was released in June 2021. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Martin Kletzander <mkletzan@redhat.com>
2022-04-12 15:22:24 +00:00
opensuse-leap-153:
jobs:
- arch: x86_64
variables:
RPM: skip
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 10:43:37 +00: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: Switch from macOS 11 to macOS 12 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2022-08-11 10:05:24 +00:00
macos-12:
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:
ci: regenerate with lcitool manifest Two notable changes: * the macOS platform has switched from x86_64 to aarch64 * if a new pipeline starts before a previous one finishes, jobs marked 'interruptible: true' will be auto-cancelled Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-11-14 10:47:29 +00:00
- arch: aarch64
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:
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
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 14:06:19 +00:00
ubuntu-2004:
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
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
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 14:06:19 +00: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
Reference in New Issue Copy Permalink