From: "David Caro" <dcaroest(a)redhat.com&gt; To: "Sandro Bonazzola" <sbonazzo(a)redhat.com&gt; Cc: "infra" <infra(a)ovirt.org&gt;, devel(a)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.

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(a)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(a)redhat.com Web: www.redhat.com RHT Global #: 82-62605 _______________________________________________ Devel mailing list Devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

----- Original Message ----- > From: "Eyal Edri" <eedri(a)redhat.com&gt; > To: "David Caro" <dcaroest(a)redhat.com&gt; > Cc: devel(a)ovirt.org, "infra" <infra(a)ovirt.org&gt; > 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(a)redhat.com&gt; >> To: "Sandro Bonazzola" <sbonazzo(a)redhat.com&gt; >> Cc: "infra" <infra(a)ovirt.org&gt;, devel(a)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(a)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(a)redhat.com >> Web: www.redhat.com >> RHT Global #: 82-62605 >> >> _______________________________________________ >> Devel mailing list >> Devel(a)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(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

----- Original Message ----- > From: "Sandro Bonazzola" <sbonazzo(a)redhat.com&gt; > To: "Martin Perina" <mperina(a)redhat.com&gt;, "Eyal Edri" <eedri(a)redhat.com&gt; > Cc: devel(a)ovirt.org, "infra" <infra(a)ovirt.org&gt; > 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(a)redhat.com&gt; >>> To: "David Caro" <dcaroest(a)redhat.com&gt; >>> Cc: devel(a)ovirt.org, "infra" <infra(a)ovirt.org&gt; >>> 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(a)redhat.com&gt; >>>> To: "Sandro Bonazzola" <sbonazzo(a)redhat.com&gt; >>>> Cc: "infra" <infra(a)ovirt.org&gt;, devel(a)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(a)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(a)redhat.com >>>> Web: www.redhat.com >>>> RHT Global #: 82-62605 >>>> >>>> _______________________________________________ >>>> Devel mailing list >>>> Devel(a)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(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/devel >>> >> _______________________________________________ >> Infra mailing list >> Infra(a)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 >