oVirt CI should support fast moving platform releases
General
Additional Info
General
Additional Info
Description
It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right.
We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster.
This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it.
Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it.
Activity
Show:
Barak Korren June 12, 2018 at 12:34 PM
Putting this under as it seems full gating of platform changes would solve this as well.
Barak Korren June 10, 2018 at 12:35 PM
Actually I think the user story is quite simple here - "As an ovirt developer, I would like to know as early as possible if platform changes are going to break oVirt so that I can react to them in a timely manner".
Or perhaps its "As a platform component developer I would like to know if changes I make are causing issues in oVirt as early as possible so I can eliminate those issues as early as possible and have newer version of my component be adopted by oVirt".
Actually which one of the two stories above we decide to aim for has significant influence on the kind of implementation we aim for.
Medium
It's a bit hard to describe this as a user story, but the idea is to think what can we (oVirt CI) do keep oVirt stable as it is today, while taking into account the platforms that support it ( Ansible, Wildfly, CentOS, Fedora. OpenShift? ) will at some point shift to a faster release cadence which is much more frequent from today and possibly breaks oVirt users if the proper testing won't be done right.
We are already doing good things today with oVirt System Tests and change queue, but it might not flexible and scalable enough if we'll start getting releases of layered products much faster.
This solution might include tighter cooperation with the relevant CI teams for the other products, improved OST framework, and infrastructure changes to support it.
Due to the side of this effort, it should be broken down into Epics and smaller user stories while grooming it.