[libvirt] [PATCH v3] [libvirt-jenkins-ci] Build on supported Fedora releases (25-26)
Fedora 23 has been out of support for quite a while now, with Fedora 24 recently joining it with the release of Fedora 26 which, on the other hand, is fully supported and a prime candidate for building libvirt. Signed-off-by: Andrea Bolognani <abologna@redhat.com> --- Yash first attempted this last December[1], without much luck. Fedora 26 has been released in the meantime, which means we can get rid of two builders instead of one! Someone will have to prepare the 'libvirt-fedora-26' builder, though, because it doesn't exist at the moment :) [1] https://www.redhat.com/archives/libvir-list/2016-December/msg00676.html projects/libosinfo.yaml | 3 +-- projects/libvirt-cim.yaml | 3 +-- projects/libvirt-glib.yaml | 3 +-- projects/libvirt-go-xml.yaml | 3 +-- projects/libvirt-go.yaml | 3 +-- projects/libvirt-perl.yaml | 3 +-- projects/libvirt-python.yaml | 3 +-- projects/libvirt-sandbox.yaml | 3 +-- projects/libvirt-tck.yaml | 3 +-- projects/libvirt.yaml | 9 +++------ projects/osinfo-db-tools.yaml | 3 +-- projects/osinfo-db.yaml | 3 +-- projects/virt-manager.yaml | 3 +-- projects/virt-viewer.yaml | 3 +-- 14 files changed, 16 insertions(+), 32 deletions(-) diff --git a/projects/libosinfo.yaml b/projects/libosinfo.yaml index f9a8ceb..77c0414 100644 --- a/projects/libosinfo.yaml +++ b/projects/libosinfo.yaml @@ -3,9 +3,8 @@ name: libosinfo machines: - libvirt-centos-7 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: libosinfo make_env: | diff --git a/projects/libvirt-cim.yaml b/projects/libvirt-cim.yaml index 82a8127..b3476e7 100644 --- a/projects/libvirt-cim.yaml +++ b/projects/libvirt-cim.yaml @@ -4,9 +4,8 @@ machines: - libvirt-centos-6 - libvirt-centos-7 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: libvirt CIM jobs: diff --git a/projects/libvirt-glib.yaml b/projects/libvirt-glib.yaml index 7d897ab..eba4646 100644 --- a/projects/libvirt-glib.yaml +++ b/projects/libvirt-glib.yaml @@ -3,9 +3,8 @@ name: libvirt-glib machines: - libvirt-centos-7 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: Libvirt GLib jobs: diff --git a/projects/libvirt-go-xml.yaml b/projects/libvirt-go-xml.yaml index 9f45694..ebe06fb 100644 --- a/projects/libvirt-go-xml.yaml +++ b/projects/libvirt-go-xml.yaml @@ -3,9 +3,8 @@ name: libvirt-go-xml machines: - libvirt-centos-7 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: Libvirt Go XML jobs: diff --git a/projects/libvirt-go.yaml b/projects/libvirt-go.yaml index b0ebc73..9ffdd0a 100644 --- a/projects/libvirt-go.yaml +++ b/projects/libvirt-go.yaml @@ -3,9 +3,8 @@ name: libvirt-go machines: - libvirt-centos-7 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: Libvirt Go jobs: diff --git a/projects/libvirt-perl.yaml b/projects/libvirt-perl.yaml index a9f4740..7646e27 100644 --- a/projects/libvirt-perl.yaml +++ b/projects/libvirt-perl.yaml @@ -3,9 +3,8 @@ name: libvirt-perl machines: - libvirt-centos-7 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: Libvirt Perl jobs: diff --git a/projects/libvirt-python.yaml b/projects/libvirt-python.yaml index c1192d0..cae8ca7 100644 --- a/projects/libvirt-python.yaml +++ b/projects/libvirt-python.yaml @@ -4,9 +4,8 @@ machines: - libvirt-centos-6 - libvirt-centos-7 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: Libvirt Python jobs: diff --git a/projects/libvirt-sandbox.yaml b/projects/libvirt-sandbox.yaml index ebbc5be..2920084 100644 --- a/projects/libvirt-sandbox.yaml +++ b/projects/libvirt-sandbox.yaml @@ -2,9 +2,8 @@ - project: name: libvirt-sandbox machines: - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: Libvirt Sandbox jobs: diff --git a/projects/libvirt-tck.yaml b/projects/libvirt-tck.yaml index a7c0233..ca72f6c 100644 --- a/projects/libvirt-tck.yaml +++ b/projects/libvirt-tck.yaml @@ -2,9 +2,8 @@ - project: name: libvirt-tck machines: - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: Libvirt TCK jobs: diff --git a/projects/libvirt.yaml b/projects/libvirt.yaml index 5125c16..0efe770 100644 --- a/projects/libvirt.yaml +++ b/projects/libvirt.yaml @@ -4,9 +4,8 @@ machines: - libvirt-centos-6 - libvirt-centos-7 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: Libvirt archive_format: xz @@ -17,9 +16,8 @@ - libvirt-centos-6 - libvirt-centos-7 - libvirt-debian-8 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide - libvirt-freebsd - autotools-syntax-check-job: @@ -28,9 +26,8 @@ - libvirt-centos-6 - libvirt-centos-7 - libvirt-debian-8 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide check_env: | export VIR_TEST_EXPENSIVE=1 diff --git a/projects/osinfo-db-tools.yaml b/projects/osinfo-db-tools.yaml index 5f275ab..93931af 100644 --- a/projects/osinfo-db-tools.yaml +++ b/projects/osinfo-db-tools.yaml @@ -3,9 +3,8 @@ name: osinfo-db-tools machines: - libvirt-centos-7 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: osinfo database tools jobs: diff --git a/projects/osinfo-db.yaml b/projects/osinfo-db.yaml index 9539724..83eb92f 100644 --- a/projects/osinfo-db.yaml +++ b/projects/osinfo-db.yaml @@ -3,9 +3,8 @@ name: osinfo-db machines: - libvirt-centos-7 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: osinfo database jobs: diff --git a/projects/virt-manager.yaml b/projects/virt-manager.yaml index 4485d5f..a50e0ab 100644 --- a/projects/virt-manager.yaml +++ b/projects/virt-manager.yaml @@ -3,9 +3,8 @@ name: virt-manager machines: - libvirt-centos-7 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: Virtual Machine Manager jobs: diff --git a/projects/virt-viewer.yaml b/projects/virt-viewer.yaml index 06c372b..e3ef04a 100644 --- a/projects/virt-viewer.yaml +++ b/projects/virt-viewer.yaml @@ -3,9 +3,8 @@ name: virt-viewer machines: - libvirt-centos-7 - - libvirt-fedora-23 - - libvirt-fedora-24 - libvirt-fedora-25 + - libvirt-fedora-26 - libvirt-fedora-rawhide title: Virt Viewer jobs: -- 2.13.5
On Thu, Sep 07, 2017 at 12:48:22PM +0200, Andrea Bolognani wrote:
Fedora 23 has been out of support for quite a while now, with Fedora 24 recently joining it with the release of Fedora 26 which, on the other hand, is fully supported and a prime candidate for building libvirt.
Signed-off-by: Andrea Bolognani <abologna@redhat.com> --- Yash first attempted this last December[1], without much luck.
Fedora 26 has been released in the meantime, which means we can get rid of two builders instead of one! Someone will have to prepare the 'libvirt-fedora-26' builder, though, because it doesn't exist at the moment :)
Until someone actually creates the new builders for F26 and almost time for F27 now too, I don't think we should really be turning off existing builders. We really badly need someone to write a kickstart file that can 100% automate the provisioning of Fedora VMs suitable for running our CI. Then we can quickly deploy builers when new Fedora comes out and get to point where we're always 100% aligned with testing on the 2 current supported releases + rawhide. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
On Thu, 2017-09-07 at 11:58 +0100, Daniel P. Berrange wrote:
Fedora 26 has been released in the meantime, which means we can get rid of two builders instead of one! Someone will have to prepare the 'libvirt-fedora-26' builder, though, because it doesn't exist at the moment :)
Until someone actually creates the new builders for F26 and almost time for F27 now too, I don't think we should really be turning off existing builders.
I posted this in part to raise the issue of the Fedora 26 builder not being available yet, but I disagree on the fact that we can't get rid of Fedora 23 and 24 until that's in place. Building on two unsupported Fedora releases doesn't really buy us anything except for more load on the already tightly packed CI hosts.
We really badly need someone to write a kickstart file that can 100% automate the provisioning of Fedora VMs suitable for running our CI. Then we can quickly deploy builers when new Fedora comes out and get to point where we're always 100% aligned with testing on the 2 current supported releases + rawhide.
I've been working on Ansible playbooks for my development machines and I've intended from the very beginning to make them generic enough that I could use them for my own builders too with only minimal changes. Since I'm going to spend time on that regardless, I'm perfectly fine with coming up with something that can turn a freshly-installed Fedora guest into a builder suitable for the CentOS CI. As for the installation step, I've never used kickstart but I was thinking of taking advantage of the amazing work the virt-builder maintainers have been doing in quickly preparing templates after a new Fedora version has been released. How does that sound? -- Andrea Bolognani / Red Hat / Virtualization
On Thu, Sep 07, 2017 at 01:46:03PM +0200, Andrea Bolognani wrote:
On Thu, 2017-09-07 at 11:58 +0100, Daniel P. Berrange wrote:
Fedora 26 has been released in the meantime, which means we can get rid of two builders instead of one! Someone will have to prepare the 'libvirt-fedora-26' builder, though, because it doesn't exist at the moment :)
Until someone actually creates the new builders for F26 and almost time for F27 now too, I don't think we should really be turning off existing builders.
I posted this in part to raise the issue of the Fedora 26 builder not being available yet, but I disagree on the fact that we can't get rid of Fedora 23 and 24 until that's in place. Building on two unsupported Fedora releases doesn't really buy us anything except for more load on the already tightly packed CI hosts.
I would be ok with killing F23, as that brings us back to the long term load point where we have 2 stable Fedoras tested + rawhide.
We really badly need someone to write a kickstart file that can 100% automate the provisioning of Fedora VMs suitable for running our CI. Then we can quickly deploy builers when new Fedora comes out and get to point where we're always 100% aligned with testing on the 2 current supported releases + rawhide.
I've been working on Ansible playbooks for my development machines and I've intended from the very beginning to make them generic enough that I could use them for my own builders too with only minimal changes.
Since I'm going to spend time on that regardless, I'm perfectly fine with coming up with something that can turn a freshly-installed Fedora guest into a builder suitable for the CentOS CI.
As for the installation step, I've never used kickstart but I was thinking of taking advantage of the amazing work the virt-builder maintainers have been doing in quickly preparing templates after a new Fedora version has been released.
How does that sound?
Sure, using virt-builder as a starting point is fine too - the key is simply that it be 100% automatable. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
On Thu, Sep 07, 2017 at 12:48:22PM +0200, Andrea Bolognani wrote:
Fedora 23 has been out of support for quite a while now, with Fedora 24 recently joining it with the release of Fedora 26 which, on the other hand, is fully supported and a prime candidate for building libvirt.
Signed-off-by: Andrea Bolognani <abologna@redhat.com> --- Yash first attempted this last December[1], without much luck.
Fedora 26 has been released in the meantime, which means we can get rid of two builders instead of one! Someone will have to prepare the 'libvirt-fedora-26' builder, though, because it doesn't exist at the moment :)
[1] https://www.redhat.com/archives/libvir-list/2016-December/msg00676.html
projects/libosinfo.yaml | 3 +-- projects/libvirt-cim.yaml | 3 +-- projects/libvirt-glib.yaml | 3 +-- projects/libvirt-go-xml.yaml | 3 +-- projects/libvirt-go.yaml | 3 +-- projects/libvirt-perl.yaml | 3 +-- projects/libvirt-python.yaml | 3 +-- projects/libvirt-sandbox.yaml | 3 +-- projects/libvirt-tck.yaml | 3 +-- projects/libvirt.yaml | 9 +++------ projects/osinfo-db-tools.yaml | 3 +-- projects/osinfo-db.yaml | 3 +-- projects/virt-manager.yaml | 3 +-- projects/virt-viewer.yaml | 3 +-- 14 files changed, 16 insertions(+), 32 deletions(-)
Now that we have all the things automated we can finally push this patch. Reviewed-by: Pavel Hrdina <phrdina@redhat.com>
participants (3)
-
Andrea Bolognani -
Daniel P. Berrange -
Pavel Hrdina