June 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1396) Add a new 'test-system-artifacts' Standard-CI stage

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1396?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1396: -------------------------------- Epic Link: (was: OVIRT-400) > Add a new 'test-system-artifacts' Standard-CI stage > --------------------------------------------------- > > Key: OVIRT-1396 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1396 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSP...] flow implementation process. > An order to allow building and testing processes for containers to be triggered after package that are needed for them are built, we will introduce the "{{test-system-artifacts}}" standard-CI stage. > This stage will be invoked from the 'experimental' or 'change-queue-tester' pipelines jost like the existing OST-based flows. > In order to provide package and repo information to the std-CI script invoked by this stage we well need to implement OVIRT-1391 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-1508) create command line out of upstream_source_collector.py script

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1508?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1508: -------------------------------- Status: Done (was: To Do) upstream source collector code had been re-factored into two tools command-line - usrc.py and pusher.py > create command line out of upstream_source_collector.py script > -------------------------------------------------------------- > > Key: OVIRT-1508 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1508 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > The benefits we will have by moving it into a a separate script are: > 1) Not embedding the script inside Jenkins - We want to move to pipeline jobs in the future and in that matter we want to embed code in yamls as little as possible. > The way to do it is to move the upstream_source_collector.py to a seperate script that'll be called from a jenkins step. > The only embedded code will be a very short and simple code that'll get the script from upstream before actually calling it. > 2) use the script as command line tool - When developers wants to run it locally on their cloned D/S projects. > 3) Use hash as U/S projects folders - When using as command line tool, avoid looking for a way to match D/S to its U/S corresponding. > Hashing means, hash the URL of the U/S repo and name the folder you are going to clone into with the hash code. > That way, U/S folder name will be by the hash of the rep URL in the upstream_sources.yaml file. > Another benefit will be the fact that we will never use two copies of U/S clone to two different D/S repos that their U/S repo is the same -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-1508) create command line out of upstream_source_collector.py script

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1508?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1508: -------------------------------- Epic Link: (was: OVIRT-400) > create command line out of upstream_source_collector.py script > -------------------------------------------------------------- > > Key: OVIRT-1508 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1508 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > The benefits we will have by moving it into a a separate script are: > 1) Not embedding the script inside Jenkins - We want to move to pipeline jobs in the future and in that matter we want to embed code in yamls as little as possible. > The way to do it is to move the upstream_source_collector.py to a seperate script that'll be called from a jenkins step. > The only embedded code will be a very short and simple code that'll get the script from upstream before actually calling it. > 2) use the script as command line tool - When developers wants to run it locally on their cloned D/S projects. > 3) Use hash as U/S projects folders - When using as command line tool, avoid looking for a way to match D/S to its U/S corresponding. > Hashing means, hash the URL of the U/S repo and name the folder you are going to clone into with the hash code. > That way, U/S folder name will be by the hash of the rep URL in the upstream_sources.yaml file. > Another benefit will be the fact that we will never use two copies of U/S clone to two different D/S repos that their U/S repo is the same -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-1508) create command line out of upstream_source_collector.py script

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1508?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1508: -------------------------------- Epic Link: (was: OVIRT-400) > create command line out of upstream_source_collector.py script > -------------------------------------------------------------- > > Key: OVIRT-1508 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1508 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > The benefits we will have by moving it into a a separate script are: > 1) Not embedding the script inside Jenkins - We want to move to pipeline jobs in the future and in that matter we want to embed code in yamls as little as possible. > The way to do it is to move the upstream_source_collector.py to a seperate script that'll be called from a jenkins step. > The only embedded code will be a very short and simple code that'll get the script from upstream before actually calling it. > 2) use the script as command line tool - When developers wants to run it locally on their cloned D/S projects. > 3) Use hash as U/S projects folders - When using as command line tool, avoid looking for a way to match D/S to its U/S corresponding. > Hashing means, hash the URL of the U/S repo and name the folder you are going to clone into with the hash code. > That way, U/S folder name will be by the hash of the rep URL in the upstream_sources.yaml file. > Another benefit will be the fact that we will never use two copies of U/S clone to two different D/S repos that their U/S repo is the same -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-1536) Documentation about the change-queue flow

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1536?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1536: -------------------------------- Component/s: (was: oVirt CI) Documentation Change Queue > Documentation about the change-queue flow > ----------------------------------------- > > Key: OVIRT-1536 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1536 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue, Documentation > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > Add some reference documentation about the change-queue flow. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-1536) Documentation about the change-queue flow

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1536?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1536: -------------------------------- Epic Link: (was: OVIRT-400) > Documentation about the change-queue flow > ----------------------------------------- > > Key: OVIRT-1536 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1536 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > Add some reference documentation about the change-queue flow. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-1536) Documentation about the change-queue flow

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1536?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1536: -------------------------------- Epic Link: (was: OVIRT-400) > Documentation about the change-queue flow > ----------------------------------------- > > Key: OVIRT-1536 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1536 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > Add some reference documentation about the change-queue flow. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1549: -------------------------------- Epic Link: (was: OVIRT-400) > run OST as a third-party tester for OpenStack's ovsdbapp > -------------------------------------------------------- > > Key: OVIRT-1549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. > ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-1549) run OST as a third-party tester for OpenStack's ovsdbapp

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1549?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1549: -------------------------------- Epic Link: (was: OVIRT-400) > run OST as a third-party tester for OpenStack's ovsdbapp > -------------------------------------------------------- > > Key: OVIRT-1549 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1549 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > https://github.com/openstack/ovsdbapp is a python binding for openvswitch-ovn. ovirt-provider-ovn is planning to use it instead of its own implementation. > ovsdbapp developers want to make sure they do not break the ovirt use case. I would like us to follow https://docs.openstack.org/infra/system-config/third_party.html and become a third-party tester of ovsdbapp. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-1554) Get rid of old 'create_rpms' jobs

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1554?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1554: -------------------------------- Epic Link: (was: OVIRT-400) > Get rid of old 'create_rpms' jobs > --------------------------------- > > Key: OVIRT-1554 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1554 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: re-factor, standard-ci > > '*create_rpms*' jobs are the old kind of jobs that we used to have before STD-CI. We still have many of those laying around. > Here is the list for the time of writing these lines: > # vdsm_any_create-rpms_manual > # mom_any_create-rpms_manual_old > # qemu_4.1_create-rpms-el7-x86_64_merged > # qemu_4.1_create-rpms-el7-ppc64le_merged > # qemu_4.1_create-rpms-el7-x86_64_created > # qemu_4.1_create-rpms-el7-ppc64le_created > # qemu_master_create-rpms-el7-x86_64_created > # slf4j_master_create-rpms-el6-x86_64_merged > # qemu_master_create-rpms-el7-ppc64le_created > # slf4j_master_create-rpms-el6-x86_64_created > # ioprocess_0.15_create-rpms-el7-x86_64_merged > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_merged > # ioprocess_0.15_create-rpms-el7-x86_64_created > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_created > # ovirt-reports_3.6_create-rpms-el6-x86_64_merged > # ovirt-reports_3.6_create-rpms-el7-x86_64_merged > # ovirt-wgt_master_create-rpms-fc25-x86_64_merged > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_merged > # ovirt-reports_3.6_create-rpms-el6-x86_64_created > # ovirt-reports_3.6_create-rpms-el7-x86_64_created > # ovirt-wgt_master_create-rpms-fc25-x86_64_created > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_created > # python-windows_4.1_create-rpms-el7-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_created > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_created > # ovirt-hosted-engine-ha_any_create-rpms_manual_old > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_merged > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_merged > # python-windows_4.1_create-rpms-el7-x86_64_created > # python-windows_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_created > # py2exe-py2.7_master_create-rpms-fc25-x86_64_merged > # python-windows_4.1_create-rpms-fc24-x86_64_created > # pywin32-py2.7_master_create-rpms-el7-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_merged > # vcredist-x86_master_create-rpms-fc26-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_merged > # py2exe-py2.7_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_merged > # pywin32-py2.7_master_create-rpms-el7-x86_64_created > # pywin32-py2.7_master_create-rpms-fc25-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc26-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_created > # vcredist-x86_master_create-rpms-fc26-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-fc25-x86_64_merged > # python-windows_master_create-rpms-fc26-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc25-x86_64_created > # pywin32-py2.7_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_merged > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_merged > # python-windows_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_created > # ovirt-engine-sdk-java_3.6_create-rpms-el6-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-el7-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged > # jasperreports-server_master_create-rpms-el6-x86_64_merged > # jasperreports-server_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_created > # jasperreports-server_master_create-rpms-el6-x86_64_created > # jasperreports-server_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_merged > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_created > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_created > # tmp_ovirt-hosted-engine-ha_master_create-rpms-el7-x86_64_tagged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_merged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_created -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2018