<div dir="ltr">+1,<div>this will be the best suggestion.</div><div>we can try adding a manual trigger for drafts if needed, still need to check if possible.</div><div><br></div><div>e.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 9, 2015 at 9:38 AM, Eli Mesika <span dir="ltr"><<a href="mailto:emesika@redhat.com" target="_blank">emesika@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=""><br>
<br>
----- Original Message -----<br>
> From: "Barak Korren" <<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a>><br>
> To: "Amit Aviram" <<a href="mailto:aaviram@redhat.com">aaviram@redhat.com</a>><br>
> Cc: "infra" <<a href="mailto:infra@ovirt.org">infra@ovirt.org</a>><br>
> Sent: Tuesday, December 8, 2015 5:16:30 PM<br>
> Subject: Re: Actively triggering of CI jobs<br>
><br>
> > I was thinking, maybe it would be better if we will explicitly require to<br>
> > run the CI jobs when we push patches.. then only when the developer will<br>
> > need the job's feedback it will be activated. no redundant jobs will run,<br>
> > and we will wait much less for the jobs to finish when we will actually<br>
> > need<br>
> > them.<br>
<br>
</span>Why not simply submit your patches as a Draft until the point you want CI to run on them, then you can simply publish them ...<br>
This is the way I am using and it's simple ...<br>
<div class="HOEnZb"><div class="h5"><br>
> ><br>
> It seems to me that it will me too easy to forget to run the CI this way.<br>
><br>
> There is another way though - To make the jobs do a lot less work.<br>
> Most anything has to do what what actually happens in CI resides in<br>
> the project`s automation directory now days (see [1]). If you want to<br>
> make CI smarter so it will not do things it shouldn't be doing, all<br>
> you need to do is customize the automation scripts to be smarter and<br>
> run only the needed tests for the files that were changed by the<br>
> patch.<br>
><br>
> [1]: <a href="http://www.ovirt.org/CI/Build_and_test_standards" rel="noreferrer" target="_blank">http://www.ovirt.org/CI/Build_and_test_standards</a><br>
><br>
> --<br>
> Barak Korren<br>
> <a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a><br>
> RHEV-CI Team<br>
> _______________________________________________<br>
> Infra mailing list<br>
> <a href="mailto:Infra@ovirt.org">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>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org">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>
</div></div></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>