<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 4, 2016 at 10:38 AM, David Caro Estevez <span dir="ltr"><<a href="mailto:dcaro@redhat.com" target="_blank">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 04/03 20:27, Nadav Goldin wrote:<br>
> Hey David,<br>
> as part of the migration to <a href="http://jenkins.phx.ovirt.org" rel="noreferrer" target="_blank">jenkins.phx.ovirt.org</a>,I want to advance with<br>
> the Lago jobs. I already migrated<br>
> infra-puppet/infra-docs/ovirt-node/appliance/imgbased jobs, and so far they<br>
> seem all to work. As far as I understand the Lago jobs are pretty<br>
> independent so it should be rather simple. Currently there are 3 slaves<br>
> configured (fc23, el7, fc21).<br>
<br>
<br>
</span>There are only 3 fc23 slaves, having one less, duplicates the check run time,<br>
and having only one, triplicates it, can you create new slaves instead of<br>
moving them from the old jenkins? (lago is not the only one using them, so<br>
migrating all of them is not an option)<br></blockquote><div><br></div><div>Is it possible to add new slaves with the current state of pxe not working?</div><div>The ideal will be to have all new servers installed with the pxe fixed so we can deploy many more slaves.</div><div>This way we can just add lots of slaves to the new jenkins.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
<br>
><br>
> At the fist stage(until we finish the migration)<br>
> jenkins_master_deploy-configs_merged is not running, so we could control<br>
> which jobs get migrated. So if a patch to the jenkins yaml will be<br>
> introduced during the migration process it will have to be re-run manually.<br>
><br>
> After migrating I'll disable the lago jobs in <a href="http://jenkins.ovirt.org" rel="noreferrer" target="_blank">jenkins.ovirt.org</a>, so even if<br>
> JJB runs we will have only one jenkins running the CI checks.<br>
<br>
</span>Don't allow both to run anything at the same time, that will lead to confusion<br>
and branches being deleted at strange times on the github repo, if they run on<br>
one jenkins master, run them there only.<br>
<span class=""><br>
><br>
> One more question is if there are any other jobs which are dependent on the<br>
> Lago jobs(like the publishers which are dependent on all build_artifacts on<br>
> ovirt-node/appliance/node)<br>
<br>
</span>Lago is self-contained, anything lago needs (check-build-deploy) is tagged as<br>
lago*, any other job that uses lago, get's it from the repos.<br>
<span class=""><br>
><br>
> As far as I understand the only thing needed for migration is updating the<br>
> github api tokens and running JJB with *lago*.<br>
<br>
</span>And disabling the jobs on the other jenkins.<br>
The github configuration is not trivial though, the api token is valid only<br>
once and for a specific url. Also you have to configure the github hooks to<br>
point to the new jenkins (or it will not get any events), that is done at the<br>
github page, under project configuration.<br>
<span class=""><br>
><br>
> What do you think?<br>
><br>
><br>
> Thanks<br>
><br>
> Nadav.<br>
<br>
</span><span class="">> _______________________________________________<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>
--<br>
</span>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">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>
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></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHEV DevOps<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></div></div>
</div></div>