November 2017 - Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.1 - Build # 83 - Failure!
by jenkins＠jenkins.phx.ovirt.org 07 Nov '17

07 Nov '17

------=_Part_60_1711266159.1509937589124 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1= /=20 Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/8= 3/ Build Number: 83 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #83 [Yaniv Kaul] Install multiple hosts faster - in the perf. suite. ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 004_basic_sanity.snapshot_merge Error Message: status: 404 reason: Not Found detail: Entity not found: null -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function <lambda> a= t 0x37455f0> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, i= n assert_equals_within res =3D func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.1/ovirt= -system-tests/hc-basic-suite-4.1/test-scenarios/004_basic_sanity.py", line = 203, in <lambda> (len(api.vms.get(VM0_NAME).snapshots.list()) =3D=3D 2) and File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py= ", line 34602, in list headers=3D{"All-Content":all_content} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 46, in get return self.request(method=3D'GET', url=3Durl, headers=3Dheaders, cls= =3Dcls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 122, in request persistent_auth=3Dself.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body= ) RequestError:=20 status: 404 reason: Not Found detail: Entity not found: null --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTes= t self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, i= n wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in= wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 68, in= wrapper return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.1/ovirt= -system-tests/hc-basic-suite-4.1/test-scenarios/004_basic_sanity.py", line = 202, in snapshot_merge lambda: File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 267, i= n assert_true_within_short assert_equals_within_short(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 251, i= n assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=3Dallowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, i= n assert_equals_within res =3D func() File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.1/ovirt= -system-tests/hc-basic-suite-4.1/test-scenarios/004_basic_sanity.py", line = 203, in <lambda> (len(api.vms.get(VM0_NAME).snapshots.list()) =3D=3D 2) and File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py= ", line 34602, in list headers=3D{"All-Content":all_content} File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 46, in get return self.request(method=3D'GET', url=3Durl, headers=3Dheaders, cls= =3Dcls) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",= line 122, in request persistent_auth=3Dself.__persistent_auth File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 79, in do_request persistent_auth) File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connection= spool.py", line 162, in __do_request raise errors.RequestError(response_code, response_reason, response_body= ) '\r\nstatus: 404\r\nreason: Not Found\r\ndetail: Entity not found: null\n--= ------------------ >> begin captured logging << --------------------\novirt= lago.testlib: ERROR: * Unhandled exception in <function <lambda> at 0x3= 7455f0>\nTraceback (most recent call last):\n File "/usr/lib/python2.7/sit= e-packages/ovirtlago/testlib.py", line 219, in assert_equals_within\n re= s =3D func()\n File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-s= uite-4.1/ovirt-system-tests/hc-basic-suite-4.1/test-scenarios/004_basic_san= ity.py", line 203, in <lambda>\n (len(api.vms.get(VM0_NAME).snapshots.li= st()) =3D=3D 2) and\n File "/usr/lib/python2.7/site-packages/ovirtsdk/infr= astructure/brokers.py", line 34602, in list\n headers=3D{"All-Content":a= ll_content}\n File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructu= re/proxy.py", line 46, in get\n return self.request(method=3D\'GET\', ur= l=3Durl, headers=3Dheaders, cls=3Dcls)\n File "/usr/lib/python2.7/site-pac= kages/ovirtsdk/infrastructure/proxy.py", line 122, in request\n persiste= nt_auth=3Dself.__persistent_auth\n File "/usr/lib/python2.7/site-packages/= ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request\n pe= rsistent_auth)\n File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastru= cture/connectionspool.py", line 162, in __do_request\n raise errors.Requ= estError(response_code, response_reason, response_body)\nRequestError: \r\n= status: 404\r\nreason: Not Found\r\ndetail: Entity not found: null\n-------= -------------- >> end captured logging << ---------------------' ------=_Part_60_1711266159.1509937589124--

1 1

oVirt infra daily report - unstable production jobs - 497
by jenkins＠jenkins.phx.ovirt.org 07 Nov '17

07 Nov '17

------=_Part_80_963123067.1510009202987 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/497//artifact/exported-a… Cheers, Jenkins ------=_Part_80_963123067.1510009202987 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 06/11/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_ansible-suite-master/">ovirt-system-tests_ansible-suite-master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.1/">ovirt-system-tests_hc-basic-suite-4.1</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-sync_mirrors-centos-extras-el7-x86_64/">system-sync_mirrors-centos-extras-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/">system-sync_mirrors-centos-updates-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_80_963123067.1510009202987--

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by danken (oVirt JIRA) 06 Nov '17

06 Nov '17

This is a multi-part message in MIME format... ------------=_1510006351-29159-205 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] danken commented on OVIRT-1743: ------------------------------- > Could it be that the project contains too much independent stuff in it? I suppose this is not a joke, so I'll answer it seriously. Yes. Vdsm and Engine are too big and complex. Regardless, commit/fail/revert/fix is a frustrating development model. post/test/fix/commit is so much better. > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > Labels: change-queue > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1510006351-29159-205 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ]</pre> <h3>danken commented on OVIRT-1743:</h3> <blockquote><p>Could it be that the project contains too much independent stuff in it?</p></blockquote> <p>I suppose this is not a joke, so I'll answer it seriously. Yes. Vdsm and Engine are too big and complex.</p> <p>Regardless, commit/fail/revert/fix is a frustrating development model. post/test/fix/commit is so much better.</p> <blockquote><h3>ci please build and send to OST</h3> <pre> Key: OVIRT-1743 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: danken Assignee: infra Labels: change-queue</pre> <p>Can you please automate the frequent process, which is slow and error prone? I am writing a patch, and would like to test it in ost. now I need to</p> <ul><li><p>“ci please build”</p></li> <li><p>copy el7 url</p></li> <li><p>wait for el7 build to finish</p></li> <li><p>copy artifacts url to ovirt--system-test-manual, start it</p></li> <li><p>copy the ost run URL to the gerrit patch, so I have it for reference of failure/success.</p></li></ul></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1510006351-29159-205--

1 0

[CQ]: 83367,13 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 06 Nov '17

06 Nov '17

Change 83367,13 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/83367/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3636/

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1743: -------------------------------- Labels: change-queue (was: ) > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > Labels: change-queue > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

This is a multi-part message in MIME format... ------------=_1509983544-29358-142 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1743: -------------------------------- Component/s: oVirt CI > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1509983544-29358-142 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1743:</h3> <pre>Component/s: oVirt CI</pre> <blockquote><h3>ci please build and send to OST</h3> <pre> Key: OVIRT-1743 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: danken Assignee: infra</pre> <p>Can you please automate the frequent process, which is slow and error prone? I am writing a patch, and would like to test it in ost. now I need to</p> <ul><li><p>“ci please build”</p></li> <li><p>copy el7 url</p></li> <li><p>wait for el7 build to finish</p></li> <li><p>copy artifacts url to ovirt--system-test-manual, start it</p></li> <li><p>copy the ost run URL to the gerrit patch, so I have it for reference of failure/success.</p></li></ul></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1509983544-29358-142--

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1743: ------------------------------------- BTW I wonder why you need to run OST manually so often. We have change gating, so when merging a breaking change, you're only breaking the particular project you merged a change into. Other, unrelated projects can keep being tested against the last known working version... Could it be that the project contains too much independent stuff in it? > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

This is a multi-part message in MIME format... ------------=_1509983341-28314-112 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1743: ------------------------------------- The process is clunky because the whole idea if having to launch stuff manually in CI is clunky. We needed to provide a useful tool, so we brought some things together to make this possible. But I wouldn't want to spend efforts around automating a process which is IMO fundamentally broken. Ideally you would just get OST results for every patch before merging it, but this requires several things: # Asynchronous result notification to Gerrit, so you can see check-patch results while OST is still running (We have that in GitHub already, but our Gerrit framework is a bit rigid still) # Submitting pre-merged patches to CQ # Merge emulation, which is to say, emulate how the code will look if all patches being tested were merged together. We have bits and pieces of everything except #3 which is by far the most complex thing to do there... Adding OVIRT-627 as a blocker > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1509983341-28314-112 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1743:</h3> <p>The process is clunky because the whole idea if having to launch stuff manually in CI is clunky.</p> <p>We needed to provide a useful tool, so we brought some things together to make this possible. But I wouldn't want to spend efforts around automating a process which is IMO fundamentally broken.</p> <p>Ideally you would just get OST results for every patch before merging it, but this requires several things:</p> <p># Asynchronous result notification to Gerrit, so you can see check-patch results while OST is still running (We have that in GitHub already, but our Gerrit framework is a bit rigid still) # Submitting pre-merged patches to CQ # Merge emulation, which is to say, emulate how the code will look if all patches being tested were merged together.</p> <p>We have bits and pieces of everything except #3 which is by far the most complex thing to do there…</p> <p>Adding OVIRT-627 as a blocker</p> <blockquote><h3>ci please build and send to OST</h3> <pre> Key: OVIRT-1743 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: danken Assignee: infra</pre> <p>Can you please automate the frequent process, which is slow and error prone? I am writing a patch, and would like to test it in ost. now I need to</p> <ul><li><p>“ci please build”</p></li> <li><p>copy el7 url</p></li> <li><p>wait for el7 build to finish</p></li> <li><p>copy artifacts url to ovirt--system-test-manual, start it</p></li> <li><p>copy the ost run URL to the gerrit patch, so I have it for reference of failure/success.</p></li></ul></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1509983341-28314-112--

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1743: -------------------------------- Epic Link: OVIRT-400 > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1743: -------------------------------- Epic Link: OVIRT-400 > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0