- Infra - oVirt List Archives

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1448: -------------------------------- Description: 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. > 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 (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1448: -------------------------------- Labels: change-queue (was: ) > 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 > -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

Barak Korren created OVIRT-1448: ----------------------------------- Summary: 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 -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1448: -------------------------------- Epic Link: OVIRT-400 > 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 > -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1447) Make change-queue report status to Gerrit
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1447?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1447: ----------------------------------- Assignee: Barak Korren (was: infra) > Make change-queue report status to Gerrit > ----------------------------------------- > > Key: OVIRT-1447 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1447 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > > While the basic capabilities for the change-queue to report to Gerrit were already implemented, this had not been enabled yet in order to avoid spamming developers with incorrect messages while the change-queue is still being tested. > Once we are confident that the change queue is working well, we can add reporting to Gerrit. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1447) Make change-queue report status to Gerrit
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

Barak Korren created OVIRT-1447: ----------------------------------- Summary: Make change-queue report status to Gerrit Key: OVIRT-1447 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1447 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra While the basic capabilities for the change-queue to report to Gerrit were already implemented, this had not been enabled yet in order to avoid spamming developers with incorrect messages while the change-queue is still being tested. Once we are confident that the change queue is working well, we can add reporting to Gerrit. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1447) Make change-queue report status to Gerrit
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1447?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1447: -------------------------------- Epic Link: OVIRT-400 > Make change-queue report status to Gerrit > ----------------------------------------- > > Key: OVIRT-1447 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1447 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > While the basic capabilities for the change-queue to report to Gerrit were already implemented, this had not been enabled yet in order to avoid spamming developers with incorrect messages while the change-queue is still being tested. > Once we are confident that the change queue is working well, we can add reporting to Gerrit. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1446) Make the change-queue jobs update the 'tested' repo
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1446?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1446: -------------------------------- Description: The 'tested' repo is currently being updated by the 'experimental' jobs, this means that as soon as something makes experimental fail, changes stop flowing into 'tested'. When the change-queue will update 'tested' only the failing changes will be blocked. Until this is done, the change queue is not really testing stuff properly, because while experimental is failing, changes that pass the CQ successfully are just dropped instead of being kept. was: The 'tested' repo is current;y being updated by the 'experimental' jobs, this means that as soon as something makes experimental fail, changes stop flowing into 'tested'. When the change-queue will update 'tested' only the failing changes will be blocked. Until this is done, the change queue is not really testing stuff properly, because while experimental is failing, changes that pass the CQ successfully are just dropped instead of being kept. > Make the change-queue jobs update the 'tested' repo > --------------------------------------------------- > > Key: OVIRT-1446 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1446 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > The 'tested' repo is currently being updated by the 'experimental' jobs, this means that as soon as something makes experimental fail, changes stop flowing into 'tested'. > When the change-queue will update 'tested' only the failing changes will be blocked. > Until this is done, the change queue is not really testing stuff properly, because while experimental is failing, changes that pass the CQ successfully are just dropped instead of being kept. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1446) Make the change-queue jobs update the 'tested' repo
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1446?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1446: -------------------------------- Epic Link: OVIRT-400 > Make the change-queue jobs update the 'tested' repo > --------------------------------------------------- > > Key: OVIRT-1446 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1446 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > The 'tested' repo is current;y being updated by the 'experimental' jobs, this means that as soon as something makes experimental fail, changes stop flowing into 'tested'. > When the change-queue will update 'tested' only the failing changes will be blocked. > Until this is done, the change queue is not really testing stuff properly, because while experimental is failing, changes that pass the CQ successfully are just dropped instead of being kept. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0

[JIRA] (OVIRT-1446) Make the change-queue jobs update the 'tested' repo
by Barak Korren (oVirt JIRA) 15 Jun '17

15 Jun '17

Barak Korren created OVIRT-1446: ----------------------------------- Summary: Make the change-queue jobs update the 'tested' repo Key: OVIRT-1446 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1446 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra The 'tested' repo is current;y being updated by the 'experimental' jobs, this means that as soon as something makes experimental fail, changes stop flowing into 'tested'. When the change-queue will update 'tested' only the failing changes will be blocked. Until this is done, the change queue is not really testing stuff properly, because while experimental is failing, changes that pass the CQ successfully are just dropped instead of being kept. -- This message was sent by Atlassian JIRA (v1000.1065.1#100048)

1 0