Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

avoid repetition in automation/*packages

Description

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.

Activity

Show:

Barak Korren June 3, 2018 at 3:39 PM

Yes. Since mock_runner is still using the '*.packages' files and not the STDCI V2 YAML. We'd need to either so a serious re-factor of 'mock_runner.sh' or write a whole new backend.

Eyal Edri June 3, 2018 at 1:20 PM

since #OVIRT‌-1629 is done, is this ticket still an issue?

Barak Korren October 24, 2017 at 5:59 PM

Adding as a blocker. The new 'automation.yaml' format will allow using the usual YAML tricks to reduce duplication between package lists.

danken July 5, 2017 at 9:10 AM

this ticket is still requested.

Barak Korren July 3, 2017 at 3:32 PM

actually it seems I linked to the wrong one. Which ticket are we using to track V2 again?

Details

Assignee

Reporter

Components

Priority

Created January 10, 2017 at 12:50 PM
Updated June 24, 2018 at 8:38 AM