[
https://ovirt-jira.atlassian.net/browse/OVIRT-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barak Korren reassigned OVIRT-1077:
-----------------------------------
Assignee: Barak Korren (was: infra)
> Create a package gating flow with OST
> -------------------------------------
>
> Key: OVIRT-1077
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1077
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Reporter: Barak Korren
> Assignee: Barak Korren
> Priority: Highest
>
> The OST flows today run on package repos that are composed wither from all
> available updates (As in the case of the 'experimental' flows) or on manually
> curated repos (As in the case of the 'older' OST flows or the manual flows).
> The existing flows lack feedback. When OST fails it can be hard to know which
> of the group of changes that happened before it ran was the one to cause to
> to fail. This places a severe workload on the infra team to diagnose and
> report OST failures.
> This ticket suggest the creation of a new flow where all changes to all OST
> input sources are tracked, so that when OST fails it is possible to run a
> bisection algorithm and automatically report to the developers about the
> change that caused the failure.
> This approach can more cheaply provide most of the benefits of pre-merge
> gating while side-stepping some of the technical complications.
--
This message was sent by Atlassian JIRA
(v1000.695.3#100025)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
