<div dir="ltr"><div>Hi oVirt developers,</div><div><br></div>A few weeks ago we announced that it is now possible to run oVirt System Tests on any open patch in oVirt [1].<div>Just wanted to remind everyone how easy it to run the whole basic suite or upgrade suite on your open patches.</div><div><br></div><div>Here is a summary of the steps needed to run the job [2]:</div><div><pre style="white-space:pre-wrap;color:rgb(0,0,0)"><b>How to use?</b>
</pre><pre><ul><li><span style="white-space:pre-wrap"><pre style="white-space:pre-wrap"><font color="#000000">Add a comment to your open patch in Gerrit and write '</font><b><font color="#38761d">ci please build</font></b><font color="#000000">'</font></pre></span></li><li><pre style="white-space:pre-wrap">Wait for the 'build-on-demand' job to finish and copy the URL of the build that shows up on the comments in Gerrit.</pre></li><li><pre style="white-space:pre-wrap">Go the manual job [2] and click 'Build with parameters' [3]</pre></li><li><pre style="white-space:pre-wrap"><pre style="white-space:pre-wrap;color:rgb(0,0,0)">Add your 'build-on-demand' URLs to the job (you can put multiple URLs, one per line)</pre></pre></li><li><pre style="white-space:pre-wrap"><pre style="white-space:pre-wrap;color:rgb(0,0,0)">Choose the oVirt version you wish to test (should match to the oVirt version of your patch).</pre></pre></li><li><pre style="white-space:pre-wrap;color:rgb(0,0,0)"><pre style="white-space:pre-wrap">Choose the suite type from the drop-down menu (choose basic to run normal sanity or upgrade to test upgrade engine)</pre></pre></li></ul></pre><pre style="white-space:pre-wrap;color:rgb(0,0,0)"><br></pre><pre style="white-space:pre-wrap;color:rgb(0,0,0)">There are other options to choose, but the default ones will work best for most cases,</pre><pre style="white-space:pre-wrap;color:rgb(0,0,0)">You can checkout the documentation [4] for more detailed info.</pre><pre style="white-space:pre-wrap;color:rgb(0,0,0)"><br></pre><pre style="white-space:pre-wrap;color:rgb(0,0,0)">Feel free to reach out to infra team for more info or help!</pre><pre style="white-space:pre-wrap;color:rgb(0,0,0)"><br></pre><div>[1] <a href="https://lists.ovirt.org/pipermail/devel/2017-February/029565.html">https://lists.ovirt.org/pipermail/devel/2017-February/029565.html</a><br><div>[2] <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_manual/">http://jenkins.ovirt.org/job/ovirt-system-tests_manual/</a></div><div>[3] make sure you have the 'dev' role for Jenkins, if you don't, send email to <a href="mailto:infra-support@ovirt.org">infra-support@ovirt.org</a> and ask to be added.</div><div>[4] <a href="http://ovirt-system-tests.readthedocs.io/en/latest/docs/CI/developers_info.html">http://ovirt-system-tests.readthedocs.io/en/latest/docs/CI/developers_info.html</a><br clear="all"><div><br></div>-- <br><div class="gmail_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: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div></div></div>
</div></div></div></div>