8:04 p.m.
------=_Part_3005125_1496472079.1483639443872
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
It's not. I skimmed the article too quick and saw CI and my brain added the L (CLI)
Regards,
Logan
----- On Jan 5, 2017, at 11:45 AM, Eyal Edri <eedri(a)redhat.com> wrote:
| I'm not sure I follow how CLI is related to the job, ost is using the ovirt
| python sdk to run the tests.
| On Jan 5, 2017 3:36 PM, "Logan Kuhn" < logank(a)wolfram.com > wrote:
|| Isn't the CLI going away in the semi-near future?
|| Regards,
|| Logan
|| ----- On Jan 4, 2017, at 9:31 AM, Eyal Edri < eedri(a)redhat.com > wrote:
||| FYI,
||| 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.
||| You can read all the details and how-to in the new oVirt blog [1].
||| 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.
||| 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.
||| So the 2 steps you'll need to do are:
||| 1. 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)
||| 2. Run the manual OST job for the version you'd like to test with the URLs you
||| got from #1
||| 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.
||| Please feel free to ask questions on infra(a)ovirt.org as usual.
||| [1] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/
||| --
||| Eyal Edri
||| Associate Manager
||| RHV DevOps
||| EMEA ENG Virtualization R&D
||| Red Hat Israel
||| phone: +972-9-7692018
||| irc: eedri (on #tlv #rhev-dev #rhev-integ)
||| _______________________________________________
||| Users mailing list
||| Users(a)ovirt.org
||| http://lists.ovirt.org/mailman/listinfo/users
------=_Part_3005125_1496472079.1483639443872
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><body><div style=3D"font-family: Arial; font-size: 12pt; color:
#0000=
00"><div>It's not. I skimmed the article too quick and saw CI
and my =
brain added the L (CLI)</div><div><br></div><div
data-marker=3D"__SIG_PRE__=
">Regards,<br>Logan</div><br><span id=3D"zwchr"
data-marker=3D"__DIVIDER__"=
----- On Jan 5, 2017, at 11:45 AM, Eyal Edri
&lt;eedri(a)redhat.com&gt; wrot=
e:<br></span><div
data-marker=3D"__QUOTED_TEXT__"><blockquote style=3D"bord=
er-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=3D"auto">I'm not
sure I follow h=
ow CLI is related to the job, ost is using the ovirt python sdk to ru=
n the tests. </div><div
class=3D"gmail_extra"><br><div class=3D"gmail_=
quote">On Jan 5, 2017 3:36 PM, "Logan Kuhn" <<a
href=3D"mailto:logank@wo=
lfram.com" target=3D"_blank">logank(a)wolfram.com</a>&gt;
wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc
so=
lid;padding-left:1ex"><div><div
style=3D"font-family:Arial;font-size:12pt;c=
olor:#000000"><div>Isn't the CLI going away in the semi-near
future?</div><=
br><div>Regards,<br>Logan</div><br><span
id=3D"m_1464090472506595548zwchr">=
----- On Jan 4, 2017, at 9:31 AM, Eyal Edri <<a href=3D"mailto:eedri@red=
hat.com" target=3D"_blank">eedri(a)redhat.com</a>&gt;
wrote:<br></span><div><=
blockquote style=3D"border-left:2px solid #1010ff;margin-left:5px;padding-l=
eft:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:non=
e;font-family:Helvetica,Arial,sans-serif;font-size:12pt"><div
dir=3D"ltr"><=
div>FYI,</div><br><div>After many requests from multiple developers
and tes=
ters, the oVirt CI added a new simple job that lets you run the full fledge=
d 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><d=
iv>We wanted to allow running oVirt system tests on EVERY open patch from A=
NY 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 featu=
re is enabled for that project first, its already available for ovirt-engin=
e,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 an=
d check for logs from engine and the
hosts.<br></div></div><br><div>Please =
feel free to ask questions on <a href=3D"mailto:infra@ovirt.org"
target=3D"=
_blank">infra(a)ovirt.org</a> as
usual.</div><div> </div><br>[1] <a=
href=3D"https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the...
e/"
target=3D"_blank">https://www.ovirt.org/blog/2017/01/ovirt-s...
-to-the-rescue/</a><br clear=3D"all"><br>-- <br><div
class=3D"m_14640904725=
06595548m_2768400108630572348gmail_signature"><div
dir=3D"ltr"><div><div di=
r=3D"ltr"><div><div dir=3D"ltr"><div>Eyal
Edri<br>Associate Manager</div><d=
iv>RHV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat
Israel<br><br>p=
hone: <a href=3D"tel:+972%209-769-2018"
target=3D"_blank">+972-9-7692018</a=
<br>irc: eedri (on #tlv #rhev-dev
#rhev-integ)</div></div></div></div></di=
v></div></div>
</div>
<br>_______________________________________________<br>Users mailing
list<b=
r><a href=3D"mailto:Users@ovirt.org"
target=3D"_blank">Users(a)ovirt.org</a><=
br><a href=3D"http://lists.ovirt.org/mailman/listinfo/users"
target=3D"_bla=
nk">http://lists.ovirt.org/mailman/listinfo/users</a></b...
iv></div></blockquote></div></div><br></blockquote></div></div></body></htm=
l>
------=_Part_3005125_1496472079.1483639443872--