[JIRA] (OVIRT-1014) avoid repetition in automation/*packages

24 Oct 2017


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

------------=_1508867991-21521-355
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Barak Korren reassigned OVIRT-1014:
-----------------------------------

    Assignee: Daniel Belenky  (was: infra)
...
avoid repetition in automation/*packages
----------------------------------------
Key: OVIRT-1014
                URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014
            Project: oVirt - virtualization made easy
         Issue Type: New Feature
         Components: oVirt CI
           Reporter: danken
           Assignee: Daniel Belenky
             Labels: standard-ci
Currently we have many automation/*packages* files, mostly repeating each other.
Most of the information there is then repeated in vdsm.spec as well.
It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7.
It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100068)

------------=_1508867991-21521-355
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.p... ]</pre>
<h3>Barak Korren reassigned OVIRT-1014:</h3>
<pre>Assignee: Daniel Belenky  (was: infra)</pre>
<blockquote><h3>avoid repetition in automation/*packages</h3>
<pre>     Key: OVIRT-1014
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014
 Project: oVirt - virtualization made easy
         Issue Type: New Feature
         Components: oVirt CI
Reporter: danken
Assignee: Daniel Belenky
  Labels: standard-ci</pre>
<p>Currently we have many automation/*packages* files, mostly repeating each other. Most of the information there is then repeated in vdsm.spec as well. It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file.</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100068)</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>

------------=_1508867991-21521-355--

Barak Korren (oVirt JIRA)

tags

participants (1)