[JIRA] (OVIRT-1745) Make upstream source collection and polling code usable for pipelines

[Barak Korren (oVirt JIRA)]

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

Barak Korren commented on OVIRT-1745:
-------------------------------------

Work done in OVIRT-1746 provided stand-alone tools that are usable from pipelines. No further work is needed in this ticket.

> Make upstream source collection and polling code usable for pipelines
> ---------------------------------------------------------------------
>
>                 Key: OVIRT-1745
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1745
>             Project: oVirt - virtualization made easy
>          Issue Type: New Feature
>          Components: oVirt CI
>            Reporter: Barak Korren
>            Assignee: infra
>              Labels: poll-upstream-sources, upstream-source-collector
>
> The upstream source collection and polling code is currently only suitable for use in Free-Style jobs. This is because:
> # We support having 'jenkins' repositories (Where jobs expect STDCI code to be found) use the upstream sources mechanism to get the actual code from the main 'jenkins' repo in gerrit.ovirt.org
> # This creates a situation where in order to get the STDCI code we need to run the upstream sources code
> # This creates a chicken and and egg problem because the upstream sources code is part of the STDCI code
> # To solve this issue we simply embedded the upstream sources code into the job code by using '{{#include}}' in JJB rather then running it as a stand-alone script.
> # This technique is not usable for pipelines, so we need to come with a different solution and make the required adjustments to the source collection and polling code.



--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/infra/attachments/20171228/216dbedf/attachment.html>