[ https://ovirt-jira.atlassian.net/browse/OVIRT-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barak Korren updated OVIRT-1746:

Epic Link: OVIRT-400

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
  Labels: poll-upstream-sources, upstream-source-collector

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. 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 It is desirable to have the upstream source handling code be concentrated into a single tool that resides in the ‘{{scripts}}’ directory.

— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)