<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 1, 2015 at 7:42 PM, David Caro <span dir="ltr"><<a href="mailto:dcaro@redhat.com" target="_blank" onclick="window.open('https://mail.google.com/a/https://mail.google.com/mail/u/1/?zx=h6bgwpurpc3#inbox/mail/?view=cm&tf=1&to=dcaro@redhat.com&cc=&bcc=&su=&body=','_blank');return false;">dcaro@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 12/01 19:37, Tal Nisan wrote:<br>
> Well, if the integration team is OK with that then I guess it's up to the<br>
> branch owner indeed and as said it will be very helpful for the backport<br>
> process if we indeed have CI jobs and gerrit hooks on the 3.6.1 branch for<br>
> the following weeks until 3.6.1 is released<br>
<br>
</span>Ok, waiting for reply from the integration team, not sure if all of them are<br>
monitoring the infra list though, you might ask on devel too (or cc them)<br></blockquote><div><br></div><div>From CI pov, +1 on enabling all gerrit hooks on any stable branch we add,</div><div>as far as jenkins jobs we have to be very carfeul with it, since it will mean duplicating many jobs we have right now and not sure jenkins can handle it.<br>either we decide on a limited must have sanity set of tests to run on version branches (like 3.6.1) or we can suffice with the 3.6 jobs,</div><div>since they are a superset of 3.6.1 and if something fails there it means it will fail 3.6.1, the otherway is very unlikely (i.e fail on 3.6.1 and not 3.6) so</div><div>this is why i think the extra resources and time per job that will be added to jenkins won't worth adding all the jobs.</div><div><br></div><div>e.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
><br>
> On Tue, Dec 1, 2015 at 7:30 PM, David Caro <<a href="mailto:dcaro@redhat.com" onclick="window.open('https://mail.google.com/a/https://mail.google.com/mail/u/1/?zx=h6bgwpurpc3#inbox/mail/?view=cm&tf=1&to=dcaro@redhat.com&cc=&bcc=&su=&body=','_blank');return false;">dcaro@redhat.com</a>> wrote:<br>
><br>
> > On 12/01 19:25, Tal Nisan wrote:<br>
> > > Well, it's not my decision but of the integration team, for me as the<br>
> > > stable branches maintainer it will help a lot to have the gerrit hooks<br>
> > (I'd<br>
> > > say even a must) and CI (not a must but definitely nice to have)<br>
> ><br>
> ><br>
> > I disagree on that, I think that it's the projects owners that should know<br>
> > what do they want to test and when, not the integration team.<br>
> ><br>
> > In any case, can you ask whoever makes the decision to ack?<br>
> ><br>
> > ><br>
> > > On Tue, Dec 1, 2015 at 7:23 PM, David Caro <<a href="mailto:dcaro@redhat.com" onclick="window.open('https://mail.google.com/a/https://mail.google.com/mail/u/1/?zx=h6bgwpurpc3#inbox/mail/?view=cm&tf=1&to=dcaro@redhat.com&cc=&bcc=&su=&body=','_blank');return false;">dcaro@redhat.com</a>> wrote:<br>
> > ><br>
> > > ><br>
> > > > So a couple questions here:<br>
> > > ><br>
> > > > * Who decides which branches are stable?<br>
> > > > * Who decides which branches have ci?<br>
> > > ><br>
> > > > In the latter, you can easily add the extra branch to the vdsm project<br>
> > > > yaml:<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > <a href="https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/vdsm/vdsm_standard.yaml;hb=refs/heads/master</a><br>
> > > ><br>
> > > > There on line 55, just define another version:<br>
> > > ><br>
> > > > - 3.6.1:<br>
> > > > branch: ovirt-3.6.1<br>
> > > ><br>
> > > > And the jobs will be created automatically once merged<br>
> > > ><br>
> > > ><br>
> > > > (I know, it needs a bit of a cleanup, and we are working on even not<br>
> > > > having to<br>
> > > > change any yaml, but for now it's what we have)<br>
> > > ><br>
> > > > On 12/01 10:52, Tal Nisan wrote:<br>
> > > > > The 3.6.1 branch is not treated by the hooks as a stable branch [1]<br>
> > > > > Aside for that, CI is not running on new patches there<br>
> > > > ><br>
> > > > > [1]<br>
> > > > ><br>
> > > > > - Check TM::SKIP, not in a monitored branch (ovirt-engine-3.6<br>
> > > > > ovirt-engine-3.6.0 ovirt-engine-3.5 ovirt-engine-3.4<br>
> > ovirt-engine-3.3<br>
> > > > > engine_3.2 engine_3.1 ovirt-engine-3.5.2 ovirt-engine-3.4.0<br>
> > > > > ovirt-engine-3.3.4 ovirt-engine-3.3.3 ovirt-engine-3.3.2<br>
> > > > ovirt-engine-3.3.1)<br>
> > > > > - Check merged to previous::IGNORE, Not in stable branch<br>
> > > > > (['ovirt-engine-3.6', 'ovirt-engine-3.6.0', 'ovirt-engine-3.5',<br>
> > > > > 'ovirt-engine-3.4', 'ovirt-engine-3.3', 'ovirt-engine-3.5.2',<br>
> > > > > 'ovirt-engine-3.4.0', 'ovirt-engine-3.3.4', 'ovirt-engine-3.3.3',<br>
> > > > > 'ovirt-engine-3.3.2', 'ovirt-engine-3.3.1'])<br>
> > > ><br>
> > > > > _______________________________________________<br>
> > > > > Infra mailing list<br>
> > > > > <a href="mailto:Infra@ovirt.org" onclick="window.open('https://mail.google.com/a/https://mail.google.com/mail/u/1/?zx=h6bgwpurpc3#inbox/mail/?view=cm&tf=1&to=Infra@ovirt.org&cc=&bcc=&su=&body=','_blank');return false;">Infra@ovirt.org</a><br>
> > > > > <a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
> > > ><br>
> > > ><br>
> > > > --<br>
> > > > David Caro<br>
> > > ><br>
> > > > Red Hat S.L.<br>
> > > > Continuous Integration Engineer - EMEA ENG Virtualization R&D<br>
> > > ><br>
> > > > Tel.: <a href="tel:%2B420%20532%20294%20605" value="+420532294605">+420 532 294 605</a><br>
> > > > Email: <a href="mailto:dcaro@redhat.com" onclick="window.open('https://mail.google.com/a/https://mail.google.com/mail/u/1/?zx=h6bgwpurpc3#inbox/mail/?view=cm&tf=1&to=dcaro@redhat.com&cc=&bcc=&su=&body=','_blank');return false;">dcaro@redhat.com</a><br>
> > > > IRC: dcaro|dcaroest@{freenode|oftc|redhat}<br>
> > > > Web: <a href="http://www.redhat.com" rel="noreferrer" target="_blank">www.redhat.com</a><br>
> > > > RHT Global #: 82-62605<br>
> > > ><br>
> ><br>
> > --<br>
> > David Caro<br>
> ><br>
> > Red Hat S.L.<br>
> > Continuous Integration Engineer - EMEA ENG Virtualization R&D<br>
> ><br>
> > Tel.: <a href="tel:%2B420%20532%20294%20605" value="+420532294605">+420 532 294 605</a><br>
> > Email: <a href="mailto:dcaro@redhat.com" onclick="window.open('https://mail.google.com/a/https://mail.google.com/mail/u/1/?zx=h6bgwpurpc3#inbox/mail/?view=cm&tf=1&to=dcaro@redhat.com&cc=&bcc=&su=&body=','_blank');return false;">dcaro@redhat.com</a><br>
> > IRC: dcaro|dcaroest@{freenode|oftc|redhat}<br>
> > Web: <a href="http://www.redhat.com" rel="noreferrer" target="_blank">www.redhat.com</a><br>
> > RHT Global #: 82-62605<br>
> ><br>
<br>
--<br>
David Caro<br>
<br>
Red Hat S.L.<br>
Continuous Integration Engineer - EMEA ENG Virtualization R&D<br>
<br>
Tel.: <a href="tel:%2B420%20532%20294%20605" value="+420532294605">+420 532 294 605</a><br>
Email: <a href="mailto:dcaro@redhat.com" onclick="window.open('https://mail.google.com/a/https://mail.google.com/mail/u/1/?zx=h6bgwpurpc3#inbox/mail/?view=cm&tf=1&to=dcaro@redhat.com&cc=&bcc=&su=&body=','_blank');return false;">dcaro@redhat.com</a><br>
IRC: dcaro|dcaroest@{freenode|oftc|redhat}<br>
Web: <a href="http://www.redhat.com" rel="noreferrer" target="_blank">www.redhat.com</a><br>
RHT Global #: 82-62605<br>
</div></div><br>_______________________________________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org" onclick="window.open('https://mail.google.com/a/https://mail.google.com/mail/u/1/?zx=h6bgwpurpc3#inbox/mail/?view=cm&tf=1&to=Infra@ovirt.org&cc=&bcc=&su=&body=','_blank');return false;">Infra@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Eyal Edri<br>Supervisor, RHEV CI<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div>
</div></div>