This is a multi-part message in MIME format... ------------=_1510046714-26505-534 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1746?page=com.atlassian.jira.p... ] Barak Korren reassigned OVIRT-1746: ----------------------------------- Assignee: Barak Korren (was: infra)
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: Barak Korren 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) ------------=_1510046714-26505-534 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1746?page=com.atlassian.jira.p... ]</pre> <h3>Barak Korren reassigned OVIRT-1746:</h3> <pre>Assignee: Barak Korren (was: infra)</pre> <blockquote><h3>Make stand-alone upstream source collection and updating tool</h3> <pre> 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: Barak Korren Labels: poll-upstream-sources, upstream-source-collector</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. 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.</p></blockquote> <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-2BCmpYLyzY..." 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> ------------=_1510046714-26505-534--