[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=35298#comment-35298 ] 

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

{quote}
I suppose this is not a joke, so I'll answer it seriously. Yes. Vdsm and Engine are too big and complex.
{quote}

Are there low-hanging fruits there? Could we improve the per-patch checking infrastructure in one way or another to reduce the need to run full OST? Will separate checking "threads" that respond asynchronously help?

{quote}
Regardless, commit/fail/revert/fix is a frustrating development model. post/test/fix/commit is so much better.
{quote}

Perhaps we can make efforts to structure patches so that commit/fail/fix can be more common then commit/fail/revert/fix? Will one or both of the following things help?
# Lower latency of CQ/OST results
# Posting CQ/OST results back directly to Gerrit



> 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/8cad9899/attachment.html>