[
https://ovirt-jira.atlassian.net/browse/OVIRT-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren updated OVIRT-1290:
--------------------------------
Summary: Re-factor OST jobs YAML to reduce duplication (was: Re-factor OST
jobs YAML the reduce duplication)
> 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: Jenkins
> 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
(v1000.870.1#100039)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
