[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
[ 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) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/TDTWAAV7TNYZZQLHFHBJUSO4HST3A2UV/
[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39834#comment-39834 ] Eyal Edri commented on OVIRT-1448: -- [~accountid:557058:5fc78873-359e-47c9-aa0b-4845b0da8143] can we close this since patch dependencies will be included as part of the Zuul deployment? > 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#100110) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/E7Y3UOGTVV2XWYXDOK3RGEJJTFY3LEEJ/
[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1448: Epic Link: OVIRT-2184 (was: 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 > 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#100087) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/AOZFRMM7APC6ERWGLOTKXYFPQQLGBOHQ/
[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1448: Epic Link: OVIRT-2184 (was: 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 > 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#100087) ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/message/SKSBZKD2JDUF33INRMKXJGRBNJVRTRY7/
[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32406#comment-32406 ] Barak Korren commented on OVIRT-1448: - Created [a patch|https://gerrit.ovirt.org/78277] to fix a code issue that would have prevented us from properly implementing dependencies for merged Gerrit changes. > 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.1068.0#100050) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
[
https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32405#comment-32405
]
Barak Korren commented on OVIRT-1448:
-
Here are some docs about how this is done in OpenStack:
https://docs.openstack.org/infra/manual/developers.html#cross-repository-dependencies
The basic Idea is that developers add a '{{Depends-On:}}' header to the commit
message follows by a 40-char Gerrit change ID.
One implication of this is that the same change ID can point to multiple
changes (same change in different branches), so we will need to query Gerrit
and find all actual changes with that ID.
> 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.1068.0#100050)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
