<div dir="auto">I'm not sure I follow how CLI is related to the job, ost is using the ovirt python sdk to run the tests. </div><div class="gmail_extra"><br><div class="gmail_quote">On Jan 5, 2017 3:36 PM, "Logan Kuhn" <<a href="mailto:logank@wolfram.com">logank@wolfram.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-family:Arial;font-size:12pt;color:#000000"><div>Isn't the CLI going away in the semi-near future?</div><div><br></div><div>Regards,<br>Logan</div><br><span id="m_1464090472506595548zwchr">----- On Jan 4, 2017, at 9:31 AM, Eyal Edri <<a href="mailto:eedri@redhat.com" target="_blank">eedri@redhat.com</a>> wrote:<br></span><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><div dir="ltr"><div>FYI,</div><br><div>After many requests from multiple developers and testers, the oVirt CI added a new simple job that lets you run the full fledged end-to-end oVirt system tests with a click of a button.</div><div>You can read all the details and how-to in the new oVirt blog [1].<br></div><br><div>We wanted to allow running oVirt system tests on EVERY open patch from ANY oVirt project, without relaying on complex building code inside the job.</div><div>Luckily we just added the 'build-on-demand' so together with it you can build any rpms you'd like and use them to run the manual job.</div><br><div>So the 2 steps you'll need to do are:</div><div><ol><li>Write 'ci please build' inside a comment on an open oVirt patch ( make sure the feature is enabled for that project first, its already available for ovirt-engine,vdsm,dashboard and vdsm-jsonrpc-java)</li><li>Run the manual OST job for the version you'd like to test with the URLs you got from #1</li></ol><div>You'll get and email once the job is done and you can browse the results and check for logs from engine and the hosts.<br></div></div><br><div>Please feel free to ask questions on <a href="mailto:infra@ovirt.org" target="_blank">infra@ovirt.org</a> as usual.</div><div> </div><br>[1] <a href="https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/" target="_blank">https://www.ovirt.org/<wbr>blog/2017/01/ovirt-system-<wbr>tests-to-the-rescue/</a><br clear="all"><br>-- <br><div class="m_1464090472506595548m_2768400108630572348gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: <a href="tel:+972%209-769-2018" target="_blank">+972-9-7692018</a><br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div></div></div>
</div>
<br>______________________________<wbr>_________________<br>Users mailing list<br><a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br><a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br></blockquote></div></div></div></blockquote></div></div>