[
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)
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
