This is a multi-part message in MIME format... ------------=_1503237983-11245-294 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34735#comment-34735 ] Barak Korren commented on OVIRT-1602: ------------------------------------- This short-cut had been asked for in 100,000 variations. I think the best approach will be to just run OST tests per-patch (aka "patch gating"). A slightly less optimal approach would be to add a "ci please test-system" command in Gerrit. This approach means we now have the make OST know how to build, that is very sub optimal IMO.
[RFE] allow passing a gerrit link to ovirt-system-tests_manual --------------------------------------------------------------
Key: OVIRT-1602 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1602 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra
Hi all, How about $subject? So that when ovirt-system-tests_manual sees a gerrit link supplied in CUSTOM_REPOS, it will do by itself 'ci please build' (extra points for checking if that's already done and reusing) and use the resultant build as if that build itself was supplied in CUSTOM_REPOS, thus freeing the user from doing that? I find myself many times running 'ci please build' only to later wait until it finished and then pass that to ovirt-system-tests_manual. For projects that are very quick to build, that's a bit tedious, but not too much. But for engine builds, that take somewhat longer, I often forget this and come back later. It would have been nice to be able to do this in a "single shot". Thanks, -- Didi
-- This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059) ------------=_1503237983-11245-294 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1602?page=com.atlassian.jira.p... ]</pre> <h3>Barak Korren commented on OVIRT-1602:</h3> <p>This short-cut had been asked for in 100,000 variations.</p> <p>I think the best approach will be to just run OST tests per-patch (aka "patch gating").</p> <p>A slightly less optimal approach would be to add a “ci please test-system” command in Gerrit.</p> <p>This approach means we now have the make OST know how to build, that is very sub optimal IMO.</p> <blockquote><h3>[RFE] allow passing a gerrit link to ovirt-system-tests_manual</h3> <pre> Key: OVIRT-1602 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1602 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra</pre> <p>Hi all, How about $subject? So that when ovirt-system-tests_manual sees a gerrit link supplied in CUSTOM_REPOS, it will do by itself ‘ci please build’ (extra points for checking if that's already done and reusing) and use the resultant build as if that build itself was supplied in CUSTOM_REPOS, thus freeing the user from doing that? I find myself many times running ‘ci please build’ only to later wait until it finished and then pass that to ovirt-system-tests_manual. For projects that are very quick to build, that's a bit tedious, but not too much. But for engine builds, that take somewhat longer, I often forget this and come back later. It would have been nice to be able to do this in a “single shot”. Thanks, — Didi</p></blockquote> <p>— This message was sent by Atlassian JIRA (v1001.0.0-SNAPSHOT#100059)</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> ------------=_1503237983-11245-294--