June 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jir... ] 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)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jir... ] 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)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-1462) Generate more detailed output from change-queue tests

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1462?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1462: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Generate more detailed output from change-queue tests > ----------------------------------------------------- > > Key: OVIRT-1462 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1462 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > The change-queue tester jobs can have some additional information that may be useful for understanding issues but is not reported anywhere ATM. > This information includes: > # If the test failed because a build job failed, and which build job made it fail. > # If the test failed during OST run, which suits failed. > This information should, at least, be presented in the test results screen, but may also be preserved and included in the email or Gerrit notifications about failing changes. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-1462) Generate more detailed output from change-queue tests

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1462?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1462: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Generate more detailed output from change-queue tests > ----------------------------------------------------- > > Key: OVIRT-1462 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1462 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > The change-queue tester jobs can have some additional information that may be useful for understanding issues but is not reported anywhere ATM. > This information includes: > # If the test failed because a build job failed, and which build job made it fail. > # If the test failed during OST run, which suits failed. > This information should, at least, be presented in the test results screen, but may also be preserved and included in the email or Gerrit notifications about failing changes. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-1504) Include more patch information in CQ jobs output

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1504?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1504: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Include more patch information in CQ jobs output > ------------------------------------------------ > > Key: OVIRT-1504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1504 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > It would be useful to include more information about checked patches in the UI of the CQ jobs and in email messages generated by them. > The information to include would be: > # The patch commit message > # The patch Git SHA > # The Gerrit change ID > The information should be included in: > # The email messages sent by the change queue > # As a popup text when clicking or hovering over an icon that will be displayed for the job build in the build history. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-1504) Include more patch information in CQ jobs output

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1504?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1504: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Include more patch information in CQ jobs output > ------------------------------------------------ > > Key: OVIRT-1504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1504 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > It would be useful to include more information about checked patches in the UI of the CQ jobs and in email messages generated by them. > The information to include would be: > # The patch commit message > # The patch Git SHA > # The Gerrit change ID > The information should be included in: > # The email messages sent by the change queue > # As a popup text when clicking or hovering over an icon that will be displayed for the job build in the build history. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2185) Improve CQ output for faster debugging

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-2185: ----------------------------------- Summary: Improve CQ output for faster debugging Key: OVIRT-2185 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2185 Project: oVirt - virtualization made easy Issue Type: Epic Components: Change Queue Reporter: Barak Korren Assignee: infra As a CI/Ovirt infra team member I want reports from the change-queue to include all the information that is required to analyse, report and track the issues that it detects. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-1504) Include more patch information in CQ jobs output

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1504?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1504: -------------------------------- Component/s: (was: oVirt CI) Change Queue > Include more patch information in CQ jobs output > ------------------------------------------------ > > Key: OVIRT-1504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1504 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > It would be useful to include more information about checked patches in the UI of the CQ jobs and in email messages generated by them. > The information to include would be: > # The patch commit message > # The patch Git SHA > # The Gerrit change ID > The information should be included in: > # The email messages sent by the change queue > # As a popup text when clicking or hovering over an icon that will be displayed for the job build in the build history. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-1427) Dependencies between ovirt-engine and vdsm-jsonrpc-java

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1427?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1427: -------------------------------- Component/s: Change Queue > Dependencies between ovirt-engine and vdsm-jsonrpc-java > ------------------------------------------------------- > > Key: OVIRT-1427 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1427 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue > Reporter: Piotr Kliczewski > Assignee: infra > > Recently we had and issue that newer version of vdsm-jsonrpc-java was > available but engine spec was not updated yet. Engine patch contained spec > and module.xml changes which provided dependencies required by new version > of jsonrpc. CI used the new version of jsonrpc without engine patch being > merged which caused several issues. > This ticket is open to track how we could mitigate similar issues in the > future. > Thanks, > Piotr -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-1498) Gate lago versions with change-queue

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1498?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1498: -------------------------------- Component/s: Lago > Gate lago versions with change-queue > ------------------------------------ > > Key: OVIRT-1498 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1498 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue, Lago > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gating, lago, ost > > Lago should be considered an upstream dependency, like CentOS and libvirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2018