[ https://ovirt-jira.atlassian.net/browse/OVIRT-1602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34738#comment-34738 ]

Yedidyah Bar David commented on OVIRT-1602:

On Sun, Aug 20, 2017 at 5:06 PM, Barak Korren (oVirt JIRA)

I am not against this, but I was under the impression that part of the reason for “manual” was to ease the load on slaves.

For both of above approaches, how do you suggest to pass multiple patches/builds for different projects? Suppose I want to run ost on pending patches for otopi+host-deploy, for example.

Perhaps. I don't mind that much the architecture, I mainly want the behavior :-)) If you can suggest other means for such a “single shot” command, great.

— Didi

[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: New Feature
         Components: oVirt CI
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)