----- Original Message -----
From: "Alon Bar-Lev" <alonbl@redhat.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "infra" <infra@ovirt.org> Sent: Wednesday, January 22, 2014 4:21:35 PM Subject: Re: jenkins job to build rpms
----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "Alon Bar-Lev" <alonbl@redhat.com> Cc: "infra" <infra@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@redhat.com> To: "infra" <infra@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@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra