<html><body>
<h3>Barak Korren created OVIRT-1746:</h3>
<pre> Summary: Make stand-alone upstream source collection and updating tool
Key: OVIRT-1746
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1746
Project: oVirt - virtualization made easy
Issue Type: New Feature
Components: oVirt CI
Reporter: Barak Korren
Assignee: infra</pre>
<p>The upstream source collection code is currently built included in two different files – “{{upstream-source-collector.py}}” and “{{poll-upstream-sources.py}}”. The files reside in “{{jobs/confs/python-scripts}}” which in turn mean they are mean for embedding into jobs by JJB.</p>
<p>This situation causes several issues: # It is not easy for users to use these scripts locally, and hence its difficult to build or test repos that include upstream source dependencies locally # There is code duplication between the two python scripts # Adding certain features is harder because it requires one of the scripts to have access to code that resides in the other script (See OVIRT-1641 for example) # It is impossible to use the code from pipelines (See OVIRT-1745) # It is not east to add tests for the code</p>
<p>It is desirable to have the upstream source handling code be concentrated into a single tool that resides in the ‘{{scripts}}’ directory.</p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</p>
<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyzYS3r1Q939T2sgz1JP0ToseqkrEXn2dA2QT4K69B3tjrVkcfDZZUxPjb70rpUuEOE1js1Et-2B2ZqOx28eKsETjcrwddkRMlX8xU59ubDy7xSZtguW-2Fpav3xQjrdD31rq4X1Xs70Ne-2FIIxFV454HsOnSc1HtU1cIQ-2BLf5J6xVFOTFR2I0pnuXbQb2qkAg-3D-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>