jenkins job to build rpms

[Alon Bar-Lev]

----- Original Message -----
> From: "David Caro" <dcaroest at redhat.com>
> To: "Eyal Edri" <eedri at redhat.com>
> Cc: "infra" <infra at ovirt.org>, "Alon Bar-Lev" <alonbl at redhat.com>
> Sent: Wednesday, January 22, 2014 6:53:49 PM
> Subject: Re: jenkins job to build rpms
> 
> El mié 22 ene 2014 15:34:13 CET, Eyal Edri escribió:
> >
> >
> > ----- Original Message -----
> >> From: "Alon Bar-Lev" <alonbl at redhat.com>
> >> To: "Eyal Edri" <eedri at redhat.com>
> >> Cc: "infra" <infra at ovirt.org>
> >> Sent: Wednesday, January 22, 2014 4:21:35 PM
> >> Subject: Re: jenkins job to build rpms
> >>
> >>
> >>
> >> ----- Original Message -----
> >>> From: "Eyal Edri" <eedri at redhat.com>
> >>> To: "Alon Bar-Lev" <alonbl at redhat.com>
> >>> Cc: "infra" <infra at ovirt.org>
> >>> Sent: Wednesday, January 22, 2014 4:18:33 PM
> >>> Subject: Re: jenkins job to build rpms
> >>>
> >>> not sure i follow, can you elaborate ?
> >>> you want to consolidate all the rpm jobs into one (matrix?) job and just
> >>> add new projects/versions to it as params, rather than having a seperate
> >>> jobs
> >>> per project?
> >>
> >> yes, something like that... any method in which we have single logic.
> >
> > sounds like a good plan, need to think it over and see when we can squeeze
> > it in the tight schedule of ovirt updates we're doing right now (and we
> > have plenty).
> > i believe making sure we merge the new rpms layout and clean script is out
> > 1st priority now.
> > (after solving all infra issues and failing jobs of course).
> >
> > also, i might consider doing that after we migrate all our jobs to yaml
> > (job builder).
> > so any help in converting it is much appreciated.
> >
> > eyal.
> >
> >>
> >>>
> >>> e.
> >>>
> >>> ----- Original Message -----
> >>>> From: "Alon Bar-Lev" <alonbl at redhat.com>
> >>>> To: "infra" <infra at ovirt.org>
> >>>> Sent: Tuesday, January 21, 2014 10:27:04 PM
> >>>> Subject: jenkins job to build rpms
> >>>>
> >>>> Hi,
> >>>>
> >>>> We reached to a point in which the process of making rpms out of almost
> >>>> all
> >>>> source repositories is the same, I believe that only vdsm is an
> >>>> exception.
> >>>>
> >>>> Can we have some kind of a single job that is triggered by all the
> >>>> supported
> >>>> repos and branches and remove the repos individual jobs?
> >>>>
> >>>> Thanks,
> >>>> Alon
> >>>> _______________________________________________
> >>>> Infra mailing list
> >>>> Infra at ovirt.org
> >>>> http://lists.ovirt.org/mailman/listinfo/infra
> >>>>
> >>>
> >>
> > _______________________________________________
> > Infra mailing list
> > Infra at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> 
> Actually, once we migrate to yaml it's easier to maintain having one
> job per project, even if they run the same code, that way the histories
> do not get mixed, you can filter the jobs in the views and it's just
> one line in the yaml to add a new project.
> 
> So, if it's urgent I'll do the multiconfig manually so it's easier to
> maintain, but if it can wait, I'll do it as separated jobs in the yaml
> as it takes the best of both approaches.

It is not urgent, but will help kiril work for splitting repos and know which tarball belongs to what job and what is the timestamp.

Currently there is a need to modify all rpm jobs to produce metadata.


> 
> --
> David Caro
> 
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R&D
> 
> Email: dcaro at redhat.com
> Web: www.redhat.com
> RHT Global #: 82-62605
> 
>