[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35206#comment-35206 ]

Barak Korren commented on OVIRT-1014:

Adding OVIRT-1629 as a blocker. The new ‘{{automation.yaml}}’ format will allow using the usual YAML tricks to reduce duplication between package lists.

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: infra
  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)