[JIRA] (OVIRT-1602) [RFE] allow passing a gerrit link to ovirt-system-tests_manual

[eyal edri (oVirt JIRA)]

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

eyal edri commented on OVIRT-1602:
----------------------------------

[~didi at redhat.com] just fyi, the current manual job supports running on any projects you want, just list them one on each line. something that will be more challengin to do if you start specifying gerrit links.

The ideal solution will be to indeed enable patch gating, but it might take some time to enable, so its not feasable in the near future. 
We still need to think if its possible to support something else which won't hurt our system integrity, we are working hard to make the Jenkins system
more scalable and maintainable, and we can only do that by sticking to the architecture we designed as part of "std-ci". Implemeting a hacky solution
outside of the std-ci umbrella will bring us back to weird jenkins jobs and scripts that are hard to debug and maintain going forward.

You can try perhaps writing a local script to do it for you, something like :

1. run 'build-artifacts.sh' ( or build-on-demand ) locally via mock runner for each of the projects you want to build from and save the RPMs to local repo 
2. run the suite you want from ost repo, providing links to the local repos using the '-s' option. [1]

[1] http://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/

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