10:27 p.m.
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
4:18 p.m.
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?
e.
----- Original Message -----
From: "Alon Bar-Lev" <alonbl(a)redhat.com>
To: "infra" <infra(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
4:21 p.m.
----- Original Message -----
From: "Eyal Edri" <eedri(a)redhat.com>
To: "Alon Bar-Lev" <alonbl(a)redhat.com>
Cc: "infra" <infra(a)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.
e.
----- Original Message -----
> From: "Alon Bar-Lev" <alonbl(a)redhat.com>
> To: "infra" <infra(a)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(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
4:34 p.m.
----- Original Message -----
From: "Alon Bar-Lev" <alonbl(a)redhat.com>
To: "Eyal Edri" <eedri(a)redhat.com>
Cc: "infra" <infra(a)ovirt.org>
Sent: Wednesday, January 22, 2014 4:21:35 PM
Subject: Re: jenkins job to build rpms
----- Original Message -----
> From: "Eyal Edri" <eedri(a)redhat.com>
> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
> Cc: "infra" <infra(a)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(a)redhat.com>
> > To: "infra" <infra(a)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(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
>
6:53 p.m.
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--FOx3XaoWkcGJjImjvHTBAv0hvwXC0u2JF
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
El mi=C3=A9 22 ene 2014 15:34:13 CET, Eyal Edri escribi=C3=B3:
----- Original Message -----
> From: "Alon Bar-Lev" <alonbl(a)redhat.com>
> To: "Eyal Edri" <eedri(a)redhat.com>
> Cc: "infra" <infra(a)ovirt.org>
> Sent: Wednesday, January 22, 2014 4:21:35 PM
> Subject: Re: jenkins job to build rpms
>
>
>
> ----- Original Message -----
>> From: "Eyal Edri" <eedri(a)redhat.com>
>> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
>> Cc: "infra" <infra(a)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 j=
ust
>> add new projects/versions to it as params, rather than having
a seper=
ate
>> 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 sque=
eze
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(a)redhat.com>
>>> To: "infra" <infra(a)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 alm=
ost
>>> 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(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/infra
>>>
>>
>
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
Actually, once we migrate to yaml it's easier to maintain having one=20
job per project, even if they run the same code, that way the histories=20
do not get mixed, you can filter the jobs in the views and it's just=20
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=20
maintain, but if it can wait, I'll do it as separated jobs in the yaml=20
as it takes the best of both approaches.
--
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Email: dcaro(a)redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
--FOx3XaoWkcGJjImjvHTBAv0hvwXC0u2JF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJS3/edAAoJEEBxx+HSYmnDnZYH/AiUWJbfCPkY1h4ooPtUHepH
EgeTPIoV/8f2rtM4en6Tyom9PtEVZHEJy8YVepdBTyGJt8FjQ75+wVEalvaEs1ZK
S0z/3WDIDjHLh6Re0XhOVkeASXy/W5HIcjemOl/gSMz3s7T9exer32Az3dvcF5aG
/W+2y10DAYpHzuFlbvRjPAE+wgUIyqHB8QGDoYOZ2iUgGQRBfGlzQHXkCPSI/mVC
QFw1V01MiSVVl10SJsYAiIcRXxs+87bSxcy5JQxXFCALQ4etwt4goaGAZRobIAJd
bVa0tv1dG1z/xCvttwn+V5BxzpUbfkOZ1A0Liz/X4amWvg7hcdoYEf1AbHmc86w=
=++l1
-----END PGP SIGNATURE-----
--FOx3XaoWkcGJjImjvHTBAv0hvwXC0u2JF--
7:03 p.m.
----- Original Message -----
From: "David Caro" <dcaroest(a)redhat.com>
To: "Eyal Edri" <eedri(a)redhat.com>
Cc: "infra" <infra(a)ovirt.org>, "Alon Bar-Lev"
<alonbl(a)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(a)redhat.com>
>> To: "Eyal Edri" <eedri(a)redhat.com>
>> Cc: "infra" <infra(a)ovirt.org>
>> Sent: Wednesday, January 22, 2014 4:21:35 PM
>> Subject: Re: jenkins job to build rpms
>>
>>
>>
>> ----- Original Message -----
>>> From: "Eyal Edri" <eedri(a)redhat.com>
>>> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
>>> Cc: "infra" <infra(a)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(a)redhat.com>
>>>> To: "infra" <infra(a)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(a)ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/infra
>>>>
>>>
>>
> _______________________________________________
> Infra mailing list
> Infra(a)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(a)redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
4008
days inactive
4009
days old
5 comments
3 participants
participants (3)
-
Alon Bar-Lev -
David Caro -
Eyal Edri