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.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35295#comment-35295 ] 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.p... ]</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-2BCmpYLyzY..." 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--