[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39851#comment-39851 ] Barak Korren commented on OVIRT-1448: ------------------------------------- well, we're probably not going to implement this, but as long as we use CQ - we can still get issues where dependent patches get tested alone

Enable devs to specifiy patch dependencies for OST --------------------------------------------------

Key: OVIRT-1448 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Labels: change-queue

We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency. What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged. The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test. The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies. We would probably want to adopt OpenStack's convention here.

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