ovirt-engine related fedora 21 builds in jenkins
Hi, while dropping fc20 builds from master as announced 2 weeks ago[1] I've seen that several packages implying ovirt-engine availability on fc21 were still built on jenkins also if we dropped fc21 support for 3.6 in favor of fc22. Since there's no commitment from integration team and from infrastructure / CI team to support FC21 I would have liked to drop them. I've been stopped doing that since it seems there are developers using fc21 as development environment. I'd like to understand why. I would have understood having developers stuck on fedora 20 for supporting 3.5 and I totally understand developers already on fedora 22. But being fedora 21 the only unsupported version I don't see any real reason for keep wasting CI resources on such distribution. Is there any serious motivation for keeping fedora 21 engine related builds in jenkins? I may understand keeping vdsm related builds since vdsm is supposed to work on fc21 also for 3.5 so i've no objection in keeping vdsm and its deps on fc21 as long as vdsm team supports it. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
--MfFXiAuoTsnnDAfZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 07/08, Sandro Bonazzola wrote:
Hi, while dropping fc20 builds from master as announced 2 weeks ago[1] I've s= een that several packages implying ovirt-engine availability on fc21 were still built on jenkins also if we dropped fc21 support for 3.6 in favor o= f fc22. =20 Since there's no commitment from integration team and from infrastructure= / CI team to support FC21 I would have liked to drop them. I've been stopped doing that since it seems there are developers using fc= 21 as development environment. I'd like to understand why. =20 I would have understood having developers stuck on fedora 20 for supporti= ng 3.5 and I totally understand developers already on fedora 22. But being fedora 21 the only unsupported version I don't see any real rea= son for keep wasting CI resources on such distribution. =20 Is there any serious motivation for keeping fedora 21 engine related buil= ds in jenkins? I may understand keeping vdsm related builds since vdsm is supposed to wo= rk on fc21 also for 3.5 so i've no objection in keeping vdsm and its deps on fc21 as long as vdsm team supports it.
Totally agree, that will also allow us to remove all the fc21 slaves and replace them with fc22 or el7/el6. There are though a few projecs that still use fc21, but luckilly they use m= ock already and don't care much of what system has installed.
=20 Thanks, --=20 Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --MfFXiAuoTsnnDAfZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVnRN0AAoJEEBxx+HSYmnDdGMH/2hTmzk67W4mC8eTeRcQvDbY Z9lYadyH4XqRI+hYjz2BGHwHOvuM2/w1cPR2XtIetRo2U48VNzdUnqz3AqUhNocS w/xvhVVq9JqHOAu5a4re5M6bt/FKVhqaIwumq+rxX59OxaIKee3sG8yVa7ILMxFo r8Fs/19qpygyv6Wvo6AJ/47VVi9465DKp6OeNyjE6lLPVAlvsMI83+3uTXogcbAz htExnm93vj/6XWeLj6AIa6j4tGm7Tym466RZ8SfrmGuhkAZc63Nm+v+kws2R4img S/awB6fqpNprJ1ZAbkTAdroeDZM7Z2u34Cjmnr/gvLFDlH2EewNC5DoNwavnX/4= =xciU -----END PGP SIGNATURE----- --MfFXiAuoTsnnDAfZ--
----- Original Message -----
From: "David Caro" <dcaroest@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "infra" <infra@ovirt.org>, devel@ovirt.org Sent: Wednesday, July 8, 2015 3:11:32 PM Subject: Re: [ovirt-devel] ovirt-engine related fedora 21 builds in jenkins
On 07/08, Sandro Bonazzola wrote:
Hi, while dropping fc20 builds from master as announced 2 weeks ago[1] I've seen that several packages implying ovirt-engine availability on fc21 were still built on jenkins also if we dropped fc21 support for 3.6 in favor of fc22.
Since there's no commitment from integration team and from infrastructure / CI team to support FC21 I would have liked to drop them. I've been stopped doing that since it seems there are developers using fc21 as development environment. I'd like to understand why.
I would have understood having developers stuck on fedora 20 for supporting 3.5 and I totally understand developers already on fedora 22. But being fedora 21 the only unsupported version I don't see any real reason for keep wasting CI resources on such distribution.
Is there any serious motivation for keeping fedora 21 engine related builds in jenkins? I may understand keeping vdsm related builds since vdsm is supposed to work on fc21 also for 3.5 so i've no objection in keeping vdsm and its deps on fc21 as long as vdsm team supports it.
+1, let's focus the limited CI resources on the most important and supported OS versions.
Totally agree, that will also allow us to remove all the fc21 slaves and replace them with fc22 or el7/el6.
There are though a few projecs that still use fc21, but luckilly they use mock already and don't care much of what system has installed.
Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Eyal Edri Supervisor, RHEV CI EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "David Caro" <dcaroest@redhat.com> Cc: devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Wednesday, July 8, 2015 2:16:53 PM Subject: Re: [ovirt-devel] ovirt-engine related fedora 21 builds in jenkins
----- Original Message -----
From: "David Caro" <dcaroest@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "infra" <infra@ovirt.org>, devel@ovirt.org Sent: Wednesday, July 8, 2015 3:11:32 PM Subject: Re: [ovirt-devel] ovirt-engine related fedora 21 builds in jenkins
On 07/08, Sandro Bonazzola wrote:
Hi, while dropping fc20 builds from master as announced 2 weeks ago[1] I've seen that several packages implying ovirt-engine availability on fc21 were still built on jenkins also if we dropped fc21 support for 3.6 in favor of fc22.
Since there's no commitment from integration team and from infrastructure / CI team to support FC21 I would have liked to drop them. I've been stopped doing that since it seems there are developers using fc21 as development environment. I'd like to understand why.
I would have understood having developers stuck on fedora 20 for supporting 3.5 and I totally understand developers already on fedora 22. But being fedora 21 the only unsupported version I don't see any real reason for keep wasting CI resources on such distribution.
Is there any serious motivation for keeping fedora 21 engine related builds in jenkins? I may understand keeping vdsm related builds since vdsm is supposed to work on fc21 also for 3.5 so i've no objection in keeping vdsm and its deps on fc21 as long as vdsm team supports it.
+1, let's focus the limited CI resources on the most important and supported OS versions.
Personally I don't have any issue with the above, but please bear in mind that every engine developer currently using F21 will need to upgrade to F22 or install Centos/RHEL, because right now to develop engine we need following packages: otopi otopi-java ovirt-engine-wildfly ovirt-engine-wildfly-overlay ovirt-host-deploy ovirt-host-deploy-java And in near future we will also need: ovirt-engine-extension-aaa-jdbc So please announce some official date, from which F21 packages won't be available so we will have time to upgrade our machines. Thanks Martin
Totally agree, that will also allow us to remove all the fc21 slaves and replace them with fc22 or el7/el6.
There are though a few projecs that still use fc21, but luckilly they use mock already and don't care much of what system has installed.
Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Eyal Edri Supervisor, RHEV CI EMEA ENG Virtualization R&D Red Hat Israel
phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Il 08/07/2015 14:42, Martin Perina ha scritto:
----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "David Caro" <dcaroest@redhat.com> Cc: devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Wednesday, July 8, 2015 2:16:53 PM Subject: Re: [ovirt-devel] ovirt-engine related fedora 21 builds in jenkins
----- Original Message -----
From: "David Caro" <dcaroest@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "infra" <infra@ovirt.org>, devel@ovirt.org Sent: Wednesday, July 8, 2015 3:11:32 PM Subject: Re: [ovirt-devel] ovirt-engine related fedora 21 builds in jenkins
On 07/08, Sandro Bonazzola wrote:
Hi, while dropping fc20 builds from master as announced 2 weeks ago[1] I've seen that several packages implying ovirt-engine availability on fc21 were still built on jenkins also if we dropped fc21 support for 3.6 in favor of fc22.
Since there's no commitment from integration team and from infrastructure / CI team to support FC21 I would have liked to drop them. I've been stopped doing that since it seems there are developers using fc21 as development environment. I'd like to understand why.
I would have understood having developers stuck on fedora 20 for supporting 3.5 and I totally understand developers already on fedora 22. But being fedora 21 the only unsupported version I don't see any real reason for keep wasting CI resources on such distribution.
Is there any serious motivation for keeping fedora 21 engine related builds in jenkins? I may understand keeping vdsm related builds since vdsm is supposed to work on fc21 also for 3.5 so i've no objection in keeping vdsm and its deps on fc21 as long as vdsm team supports it.
+1, let's focus the limited CI resources on the most important and supported OS versions.
Personally I don't have any issue with the above, but please bear in mind that every engine developer currently using F21 will need to upgrade to F22 or install Centos/RHEL, because right now to develop engine we need following packages:
otopi otopi-java ovirt-engine-wildfly ovirt-engine-wildfly-overlay ovirt-host-deploy ovirt-host-deploy-java
And in near future we will also need:
ovirt-engine-extension-aaa-jdbc
So please announce some official date, from which F21 packages won't be available so we will have time to upgrade our machines.
Thanks
Let's keep them until end of the month. FC21 packages will still be built and published by Jenkins until July 31. Are 3 weeks enough?
Martin
Totally agree, that will also allow us to remove all the fc21 slaves and replace them with fc22 or el7/el6.
There are though a few projecs that still use fc21, but luckilly they use mock already and don't care much of what system has installed.
Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Eyal Edri Supervisor, RHEV CI EMEA ENG Virtualization R&D Red Hat Israel
phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Martin Perina" <mperina@redhat.com>, "Eyal Edri" <eedri@redhat.com> Cc: devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Thursday, July 9, 2015 9:43:35 AM Subject: Re: [ovirt-devel] ovirt-engine related fedora 21 builds in jenkins
Il 08/07/2015 14:42, Martin Perina ha scritto:
----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "David Caro" <dcaroest@redhat.com> Cc: devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Wednesday, July 8, 2015 2:16:53 PM Subject: Re: [ovirt-devel] ovirt-engine related fedora 21 builds in jenkins
----- Original Message -----
From: "David Caro" <dcaroest@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "infra" <infra@ovirt.org>, devel@ovirt.org Sent: Wednesday, July 8, 2015 3:11:32 PM Subject: Re: [ovirt-devel] ovirt-engine related fedora 21 builds in jenkins
On 07/08, Sandro Bonazzola wrote:
Hi, while dropping fc20 builds from master as announced 2 weeks ago[1] I've seen that several packages implying ovirt-engine availability on fc21 were still built on jenkins also if we dropped fc21 support for 3.6 in favor of fc22.
Since there's no commitment from integration team and from infrastructure / CI team to support FC21 I would have liked to drop them. I've been stopped doing that since it seems there are developers using fc21 as development environment. I'd like to understand why.
I would have understood having developers stuck on fedora 20 for supporting 3.5 and I totally understand developers already on fedora 22. But being fedora 21 the only unsupported version I don't see any real reason for keep wasting CI resources on such distribution.
Is there any serious motivation for keeping fedora 21 engine related builds in jenkins? I may understand keeping vdsm related builds since vdsm is supposed to work on fc21 also for 3.5 so i've no objection in keeping vdsm and its deps on fc21 as long as vdsm team supports it.
+1, let's focus the limited CI resources on the most important and supported OS versions.
Personally I don't have any issue with the above, but please bear in mind that every engine developer currently using F21 will need to upgrade to F22 or install Centos/RHEL, because right now to develop engine we need following packages:
otopi otopi-java ovirt-engine-wildfly ovirt-engine-wildfly-overlay ovirt-host-deploy ovirt-host-deploy-java
And in near future we will also need:
ovirt-engine-extension-aaa-jdbc
So please announce some official date, from which F21 packages won't be available so we will have time to upgrade our machines.
Thanks
Let's keep them until end of the month. FC21 packages will still be built and published by Jenkins until July 31. Are 3 weeks enough?
It's OK with me, but please do a proper announcement, because I fear that this date will get unnoticed otherwise.
Martin
Totally agree, that will also allow us to remove all the fc21 slaves and replace them with fc22 or el7/el6.
There are though a few projecs that still use fc21, but luckilly they use mock already and don't care much of what system has installed.
Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Eyal Edri Supervisor, RHEV CI EMEA ENG Virtualization R&D Red Hat Israel
phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Il 09/07/2015 09:51, Martin Perina ha scritto:
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Martin Perina" <mperina@redhat.com>, "Eyal Edri" <eedri@redhat.com> Cc: devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Thursday, July 9, 2015 9:43:35 AM Subject: Re: [ovirt-devel] ovirt-engine related fedora 21 builds in jenkins
Il 08/07/2015 14:42, Martin Perina ha scritto:
----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "David Caro" <dcaroest@redhat.com> Cc: devel@ovirt.org, "infra" <infra@ovirt.org> Sent: Wednesday, July 8, 2015 2:16:53 PM Subject: Re: [ovirt-devel] ovirt-engine related fedora 21 builds in jenkins
----- Original Message -----
From: "David Caro" <dcaroest@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "infra" <infra@ovirt.org>, devel@ovirt.org Sent: Wednesday, July 8, 2015 3:11:32 PM Subject: Re: [ovirt-devel] ovirt-engine related fedora 21 builds in jenkins
On 07/08, Sandro Bonazzola wrote:
Hi, while dropping fc20 builds from master as announced 2 weeks ago[1] I've seen that several packages implying ovirt-engine availability on fc21 were still built on jenkins also if we dropped fc21 support for 3.6 in favor of fc22.
Since there's no commitment from integration team and from infrastructure / CI team to support FC21 I would have liked to drop them. I've been stopped doing that since it seems there are developers using fc21 as development environment. I'd like to understand why.
I would have understood having developers stuck on fedora 20 for supporting 3.5 and I totally understand developers already on fedora 22. But being fedora 21 the only unsupported version I don't see any real reason for keep wasting CI resources on such distribution.
Is there any serious motivation for keeping fedora 21 engine related builds in jenkins? I may understand keeping vdsm related builds since vdsm is supposed to work on fc21 also for 3.5 so i've no objection in keeping vdsm and its deps on fc21 as long as vdsm team supports it.
+1, let's focus the limited CI resources on the most important and supported OS versions.
Personally I don't have any issue with the above, but please bear in mind that every engine developer currently using F21 will need to upgrade to F22 or install Centos/RHEL, because right now to develop engine we need following packages:
otopi otopi-java ovirt-engine-wildfly ovirt-engine-wildfly-overlay ovirt-host-deploy ovirt-host-deploy-java
And in near future we will also need:
ovirt-engine-extension-aaa-jdbc
So please announce some official date, from which F21 packages won't be available so we will have time to upgrade our machines.
Thanks
Let's keep them until end of the month. FC21 packages will still be built and published by Jenkins until July 31. Are 3 weeks enough?
It's OK with me, but please do a proper announcement, because I fear that this date will get unnoticed otherwise.
Done
Martin
Totally agree, that will also allow us to remove all the fc21 slaves and replace them with fc22 or el7/el6.
There are though a few projecs that still use fc21, but luckilly they use mock already and don't care much of what system has installed.
Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- David Caro
Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Eyal Edri Supervisor, RHEV CI EMEA ENG Virtualization R&D Red Hat Israel
phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
participants (4)
-
David Caro -
Eyal Edri -
Martin Perina -
Sandro Bonazzola