Skip to:

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

Run OST flow as a merge gate (Patch gating)

Description

Our oVirt change queue today check patches after they have been merged to the relevant projects.

When working post-merge, the change queue currently allows to separate between patches to different projects, but if a broken patch is merged into a project, the relevant branch in that project remains broken until a fix patch is merged.

This is an issue for big project like 'ovirt-engine' where there may be multiple unrelated changes that end up blocking each other.

This is also needed if we decide we want to provide system tests results to developers before things get merged.

Activity

Show:

Eyal Edri August 29, 2019 at 2:48 PM

we already are implementing Zuul as patch gating and it has open tickets tracking that work

Barak Korren January 19, 2017 at 8:08 AM

Removed Zuul from the subject as we're probably not going to use it.

Barak Korren December 1, 2016 at 10:56 AM
Edited

Changed subject to perhaps make it clearer

Barak Korren December 1, 2016 at 10:55 AM

talks about using Zuul for gating (It mentions check_merged but I'm guessing this is just part of the gating process).
But maybe we should have separate tickets because we will probably implement this in phases:

  1. Setup Zuul

  2. Make Zull manage check_patch

  3. Make Zuul run check_merged as a gate

  4. Add experimental flow to the gate

So I'm guessing this ticket is the 4th part...

Eyal Edri December 1, 2016 at 10:49 AM

Might be, if 734 also talks about creating a new flow to mimik/replease the existing 'deploy to experimental' + 'test experimental' then yes, its a duplicate.
If it just includes the framework work needed to connect Zuul to Gerrit, then no.

Duplicate

Details

Assignee

Reporter

Components

Priority

Created July 10, 2016 at 9:41 AM
Updated August 29, 2019 at 2:48 PM
Resolved August 29, 2019 at 2:48 PM