[libvirt] [jenkins-ci PATCH 0/2] Drop Ubuntu 16.04

Andrea Bolognani posted 2 patches 5 years ago
Failed in applying to current master (apply log)
guests/host_vars/libvirt-ubuntu-16/docker.yml |  2 --
.../host_vars/libvirt-ubuntu-16/install.yml   |  2 --
guests/host_vars/libvirt-ubuntu-16/main.yml   | 22 -------------------
guests/inventory                              |  1 -
guests/playbooks/build/jobs/defaults.yml      |  1 -
.../playbooks/build/projects/libvirt-dbus.yml |  5 +----
.../build/projects/libvirt-go-xml.yml         |  1 -
.../playbooks/build/projects/libvirt-go.yml   |  1 -
.../build/projects/libvirt-ocaml.yml          |  1 -
.../build/projects/libvirt-sandbox.yml        |  1 -
.../playbooks/build/projects/libvirt-tck.yml  |  1 -
guests/playbooks/build/projects/libvirt.yml   |  1 -
guests/playbooks/build/projects/osinfo-db.yml |  1 -
.../playbooks/build/projects/virt-manager.yml |  4 +---
guests/vars/mappings.yml                      |  3 ---
15 files changed, 2 insertions(+), 45 deletions(-)
delete mode 100644 guests/host_vars/libvirt-ubuntu-16/docker.yml
delete mode 100644 guests/host_vars/libvirt-ubuntu-16/install.yml
delete mode 100644 guests/host_vars/libvirt-ubuntu-16/main.yml
[libvirt] [jenkins-ci PATCH 0/2] Drop Ubuntu 16.04
Posted by Andrea Bolognani 5 years ago
I'm a bit conflicted about this one: on one hand, unlike Debian 8 we
haven't really run into any issue with Ubuntu 16.04, we can still
build almost all projects on it, and it doesn't require any crazy
hacks to maintain; on the other hand, perhaps the reason why we still
claim we can build almost all projects on it is because we don't
actually run any build on it, either on CentOS CI or on Travis CI :D

Anyway: here are the patches, let's see what other people think.

Andrea Bolognani (2):
  Stop building on Ubuntu 16.04
  guests: Drop Ubuntu 18.04

 guests/host_vars/libvirt-ubuntu-16/docker.yml |  2 --
 .../host_vars/libvirt-ubuntu-16/install.yml   |  2 --
 guests/host_vars/libvirt-ubuntu-16/main.yml   | 22 -------------------
 guests/inventory                              |  1 -
 guests/playbooks/build/jobs/defaults.yml      |  1 -
 .../playbooks/build/projects/libvirt-dbus.yml |  5 +----
 .../build/projects/libvirt-go-xml.yml         |  1 -
 .../playbooks/build/projects/libvirt-go.yml   |  1 -
 .../build/projects/libvirt-ocaml.yml          |  1 -
 .../build/projects/libvirt-sandbox.yml        |  1 -
 .../playbooks/build/projects/libvirt-tck.yml  |  1 -
 guests/playbooks/build/projects/libvirt.yml   |  1 -
 guests/playbooks/build/projects/osinfo-db.yml |  1 -
 .../playbooks/build/projects/virt-manager.yml |  4 +---
 guests/vars/mappings.yml                      |  3 ---
 15 files changed, 2 insertions(+), 45 deletions(-)
 delete mode 100644 guests/host_vars/libvirt-ubuntu-16/docker.yml
 delete mode 100644 guests/host_vars/libvirt-ubuntu-16/install.yml
 delete mode 100644 guests/host_vars/libvirt-ubuntu-16/main.yml

-- 
2.20.1

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [jenkins-ci PATCH 0/2] Drop Ubuntu 16.04
Posted by Daniel P. Berrangé 5 years ago
On Thu, Mar 28, 2019 at 05:57:57PM +0100, Andrea Bolognani wrote:
> I'm a bit conflicted about this one: on one hand, unlike Debian 8 we

I don't see a conflict. As your first patch says, our support policy
has eliminated this distro version, so there's no reason to have it
in CI.

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 :|

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [jenkins-ci PATCH 0/2] Drop Ubuntu 16.04
Posted by Andrea Bolognani 5 years ago
On Thu, 2019-03-28 at 17:37 +0000, Daniel P. Berrangé wrote:
> On Thu, Mar 28, 2019 at 05:57:57PM +0100, Andrea Bolognani wrote:
> > I'm a bit conflicted about this one: on one hand, unlike Debian 8 we
> 
> I don't see a conflict. As your first patch says, our support policy
> has eliminated this distro version, so there's no reason to have it
> in CI.

Alright! ACKs then? O:-)

-- 
Andrea Bolognani / Red Hat / Virtualization

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [jenkins-ci PATCH 0/2] Drop Ubuntu 16.04
Posted by Pavel Hrdina 5 years ago
On Thu, Mar 28, 2019 at 05:57:57PM +0100, Andrea Bolognani wrote:
> I'm a bit conflicted about this one: on one hand, unlike Debian 8 we
> haven't really run into any issue with Ubuntu 16.04, we can still
> build almost all projects on it, and it doesn't require any crazy
> hacks to maintain; on the other hand, perhaps the reason why we still
> claim we can build almost all projects on it is because we don't
> actually run any build on it, either on CentOS CI or on Travis CI :D
> 
> Anyway: here are the patches, let's see what other people think.
> 
> Andrea Bolognani (2):
>   Stop building on Ubuntu 16.04
>   guests: Drop Ubuntu 18.04

Reviewed-by: Pavel Hrdina <phrdina@redhat.com>
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [jenkins-ci PATCH 0/2] Drop Ubuntu 16.04
Posted by Andrea Bolognani 5 years ago
On Thu, 2019-03-28 at 17:57 +0100, Andrea Bolognani wrote:
> I'm a bit conflicted about this one: on one hand, unlike Debian 8 we
> haven't really run into any issue with Ubuntu 16.04, we can still
> build almost all projects on it, and it doesn't require any crazy
> hacks to maintain; on the other hand, perhaps the reason why we still
> claim we can build almost all projects on it is because we don't
> actually run any build on it, either on CentOS CI or on Travis CI :D
> 
> Anyway: here are the patches, let's see what other people think.

On the other (other!) hand, with Debian 8 out of the picture dropping
Ubuntu 16.04 would mean the oldest QEMU version we'd have to support
would be 2.8 rather than 2.5, which would probably result in slightly
more dead code being eligible for removal. I'd be okay with that.

-- 
Andrea Bolognani / Red Hat / Virtualization

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list