<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 17, 2017 at 10:36 AM, Michal Skrivanek <span dir="ltr">&lt;<a href="mailto:michal.skrivanek@redhat.com" target="_blank">michal.skrivanek@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><span class=""><blockquote type="cite"><div>On 17 Feb 2017, at 16:16, Yaniv Kaul &lt;<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>&gt; wrote:</div><br class="m_-4708172503991622187Apple-interchange-newline"><div><div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Feb 17, 2017 2:04 PM, &quot;Michal Skrivanek&quot; &lt;<a href="mailto:michal.skrivanek@redhat.com" target="_blank">michal.skrivanek@redhat.com</a>&gt; wrote:<br type="attribution"><blockquote class="m_-4708172503991622187quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div class="m_-4708172503991622187quoted-text"><blockquote type="cite"><div>On 17 Feb 2017, at 12:25, Sandro Bonazzola &lt;<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>&gt; wrote:</div><br class="m_-4708172503991622187m_-7842688921910176839Apple-interchange-newline"><div><div dir="ltr"><div>Build job is failing:</div><a href="http://jenkins.ovirt.org/user/sbonazzo/my-views/view/Builders/job/ovirt-web-ui_4.1_github_build-artifacts-el7-x86_64/9/artifact/exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.build-artifacts.sh/build-artifacts.sh.log" target="_blank">http://jenkins.ovirt.org/user/<wbr>sbonazzo/my-views/view/Builder<wbr>s/job/ovirt-web-ui_4.1_github_<wbr>build-artifacts-el7-x86_64/9/<wbr>artifact/exported-artifacts/<wbr>mock_logs/mocker-epel-7-x86_<wbr>64.el7.build-artifacts.sh/<wbr>build-artifacts.sh.log</a><div><br></div><div><pre>error &quot;jquery-3.1.1.tgz&quot;: Tarball is not in network and can not be located in</pre><pre>cache (&quot;/usr/share/ovirt-engine-node<wbr>js-modules/yarn-offline-cache/<wbr>jquery-3.1.1.tgz”)</pre></div></div></div></blockquote><div><br></div></div>the move to yarn still has not been fully completed and is pending merges to both webui and ovirt-engine-nodejs-module<wbr>s</div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">What&#39;s the ETA to unbreaking the build? </div><div dir="auto">A move to yarn is not a great excuse to breakage. </div></div></div></blockquote><div><br></div></span>right, but I hope it is a reminder for future not to overhaul the build system shared by 3 different sub projects right around 4.1/4.1.1 GA</div></div></blockquote><div><br></div><div>You&#39;re absolutely right, Michal. I&#39;m sorry, this is my fault. None of our JavaScript tooling parallels the oVirt release schedule, and so we were working with an eye on oVirt master, but it affected 4.1 inadvertently. Basically we were trying to make use of yarn optional in the new tooling, but it didn&#39;t work out. I should have thought of 4.1 and suggested we abort/postpone the effort instead of pushing forward.</div><div><br></div><div>Greg</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><span class=""><div><br><blockquote type="cite"><div><div dir="auto"><div dir="auto">Y. </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="m_-4708172503991622187quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div><br><blockquote type="cite"><div><div class="m_-4708172503991622187quoted-text"><div dir="ltr"><div><div><br></div>-- <br><div class="m_-4708172503991622187m_-7842688921910176839gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Sandro Bonazzola<br>Better technology. Faster innovation. Powered by community collaboration.<br>See how it works at <a href="http://redhat.com/" target="_blank">redhat.com</a></div></div></div></div></div></div></div></div>
</div></div></div>
______________________________<wbr>_________________<br>Devel mailing list<br><a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br><a href="http://lists.ovirt.org/mailman/listinfo/devel" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a></div></blockquote></div><br></div><br>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br></blockquote></div><br></div></div></div>
</div></blockquote></div><br></span></div><br>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Greg Sheremeta, MBA<br>Red Hat, Inc.<br>Sr. Software Engineer<br><a href="mailto:gshereme@redhat.com" target="_blank">gshereme@redhat.com</a><br></div></div></div>
</div></div>