[JIRA] (OVIRT-1743) ci please build and send to OST

[Barak Korren (oVirt JIRA)]

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

Barak Korren commented on OVIRT-1743:
-------------------------------------

{quote}
If OST was cheap and quick, it would be lovely to run on any patch. It can also be run after a +2 from a maintainer, or after a workflow+1, providing a verified +0.5 to a patch. I don't know if that's what you're aiming at.
{quote}

OST is probably not going to ever be cheap and quick enough.
I'm aiming at leveraging the same group-testing+bisection tech we use for post-merge OST runs. It was initially designed for pre-merge testing (a.k.a. gating) anyway, we just decided to deliver something that is useful and works before implementing everything we set out to. 

> 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)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20171107/b2a946ca/attachment.html>