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

Wednesday, 10 January 2018

This is a multi-part message in MIME format...

------------=_1515572840-15436-331
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

     [
https://ovirt-jira.atlassian.net/browse/OVIRT-1745?page=com.atlassian.jir...
]

Barak Korren updated OVIRT-1745:
--------------------------------
    Component/s:     (was: oVirt CI)
                 usrc.py
                 pusher.py

...
 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: pusher.py, usrc.py
            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)

------------=_1515572840-15436-331
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1745?page=com.atlassian.jir...
]</pre>
<h3>Barak Korren updated OVIRT-1745:</h3>
<pre>    Component/s:     (was: oVirt CI)
usrc.py
pusher.py</pre>
<blockquote><h3>Make upstream source collection and polling code usable for
pipelines</h3>
<pre>     Key: OVIRT-1745
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1745
 Project: oVirt - virtualization made easy
         Issue Type: New Feature
         Components: pusher.py, usrc.py
Reporter: Barak Korren
Assignee: infra
  Labels: poll-upstream-sources, upstream-source-collector</pre>
<p>The upstream source collection and polling code is currently only suitable for
use in Free-Style jobs. This is because: # We support having &lsquo;jenkins&rsquo;
repositories (Where jobs expect STDCI code to be found) use the upstream sources mechanism
to get the actual code from the main &lsquo;jenkins&rsquo; 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 &lsquo;{{#include}}&rsquo; 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.</p></blockquote>
<p>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)</p>

------------=_1515572840-15436-331--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011