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

Barak Korren commented on OVIRT-1743:

BTW I wonder why you need to run OST manually so often. We have change gating, so when merging a breaking change, you're only breaking the particular project you merged a change into. Other, unrelated projects can keep being tested against the last known working version…

Could it be that the project contains too much independent stuff in it?

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
Reporter: danken
Assignee: infra

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)