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

Tuesday, 24 October 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.jir...
]

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.jir...
]</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>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100068)</p>

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011