[ https://ovirt-jira.atlassian.net/browse/OVIRT-1290?page=com.atlassian.jira.p... ] Eyal Edri updated OVIRT-1290: ----------------------------- Resolution: Fixed Status: Done (was: To Do) AFAIK, all suites use the same YAML file now, and in any case, not something worth investing time in.

Re-factor OST jobs YAML to reduce duplication ---------------------------------------------

Key: OVIRT-1290 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1290 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Manual job, OST scheduled jobs Reporter: Barak Korren Assignee: infra Labels: ost, yaml

Besides the experimental flow jobs, and the manual OST job, we also have a few more jobs that run specific OST suits on a scheduled basis. Historically theses suits were written by different people and different job templates in YAML were also written for each suit. At some point we have normalized all the suit names in OST to be of the following structure: {code} <suit_type>-suit-<ovirt version> {code} This was initially done to allow the mirror injection process to find the '{{reposync-config.repo}}' file but also facilitated the creation of the generic manual OST job. Since all suites now follow the same naming convention there is no more reason to have separate YAML job templates per suit. This separation may even cause subtle issues. All the YAML OST job templates should be unified so that we'll have just one job template that is parametrized by the suite type and oVirt version. Furthermore we can probably have just one YAML project entry to create all scheduled OST jobs.

-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)