[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 96 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/96/
Build Number: 96
Build Status:  Still Failing
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #68
[Gal Ben Haim] 4.2: Backport tests from master

[Barak Korren] Fix mock_cleanup.sh trying to umount bad things

[Barak Korren] Switch fabric-ovirt to STDCI v2


Changes for Build #69
[Gal Ben Haim] 4.2: Backport tests from master


Changes for Build #70
[Gal Ben Haim] 4.2: Backport tests from master

[Sandro Bonazzola] guest agent: move to fc28

[Martin Perina] ovirt-engine: Drop FC28 build from 4.2

[arachmani] ovirt-engine-api-explorer: move from fc27 to fc 28

[arachmani] ovirt-dwh: Move from fc27 to fc28

[arachmani] ovirt-hosted-engine-ha: Move to fc28 and exclude 4.2 on fc28


Changes for Build #71
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs

[arachmani] ovirt-engine-metrics: Move to fc28 and exclude 4.2 on fc28

[arachmani] cockpit-ovirt: Move to fc28 and exclude 4.2 on fc28


Changes for Build #72
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs


Changes for Build #73
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs

[Sandro Bonazzola] ovirt-engine: exclude fc28 on 4.2.3 branch

[Sandro Bonazzola] ovirt-release: switch to fc28

[Gal Ben Haim] OST: pin HC suites to "ovirt-srv05.phx.ovirt.org"


Changes for Build #74
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs


Changes for Build #75
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs


Changes for Build #76
[Dominik Holler] network: use neutron compatible IP addresses


Changes for Build #77
[Gal Ben Haim] Adjust SSH timeout exception

[Ondra Machacek] sdk: Update to fedora 28


Changes for Build #78
[Gal Ben Haim] Adjust SSH timeout exception


Changes for Build #79
[Gal Ben Haim] Remove 4.1 suites automation files

[Daniel Belenky] DSL: Do not normalize release_branches values


Changes for Build #80
[Gal Ben Haim] Remove 4.1 suites automation files

[Sandro Bonazzola] javascript: move to fc28


Changes for Build #81
[Gal Ben Haim] Remove 4.1 suites automation files


Changes for Build #82
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing

[Sandro Bonazzola] vdsm-jsonrpc-java: switch to fc28

[Sandro Bonazzola] nsis: switch to fc28

[Sandro Bonazzola] dashboard: don't build fc28 for 4.2

[Sandro Bonazzola] mom: switch to fc28

[Sandro Bonazzola] ovirt-vmconsole: switch to fc28


Changes for Build #83
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing

[Sandro Bonazzola] ioprocess: switch to fc28

[Sandro Bonazzola] ovirt-provider-ovn: switch to fc28

[Sandro Bonazzola] log-collector: switch to fc28


Changes for Build #84
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #85
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #86
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #87
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #88
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #89
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #90
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #91
[Marcin Mirecki] network: add test validating connections between OVN  networks


Changes for Build #92
[Marcin Mirecki] network: add test validating connections between OVN  networks


Changes for Build #93
[Marcin Mirecki] network: add test validating connections between OVN  networks


Changes for Build #94
[Andrej Krejcir] HE: Test restarting HE VM


Changes for Build #95
[Andrej Krejcir] HE: Test restarting HE VM


Changes for Build #96
[Andrej Krejcir] HE: Test restarting HE VM




-
Failed Tests:
-
No tests ran.___
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/QZJV4ZOGHSWA3BUG6UEVUCV3FK4OUHEM/

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 238 - Fixed!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/238/
Build Number: 238
Build Status:  Fixed
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #237
[Andrej Krejcir] HE: Test restarting HE VM


Changes for Build #238
[Andrej Krejcir] HE: Test restarting HE VM




-
Failed Tests:
-
All tests passed___
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/FJH5EH7WY6XPAYIQLFCHVDENGXDCFNDU/

[CQ]: 91361,10 (vdsm) failed "ovirt-master" system tests

[oVirt Jenkins]

Change 91361,10 (vdsm) is probably the reason behind recent system test
failures in the "ovirt-master" change queue and needs to be fixed.

This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.

For further details about the change see:
https://gerrit.ovirt.org/#/c/91361/10

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8183/
___
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/C5B53LXVDJSA6ANQXCEBT4VX6CS6JH7B/

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 256 - Still Failing!

[jenkins]

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ 
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/256/
Build Number: 256
Build Status:  Still Failing
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #255
[Andrej Krejcir] HE: Test restarting HE VM


Changes for Build #256
[Andrej Krejcir] HE: Test restarting HE VM




-
Failed Tests:
-
No tests ran.___
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/XFKURCTMDS4NK64G2OKUP4EIRKYISYHD/

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 30 - Still Failing!

[jenkins]

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/ 
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/30/
Build Number: 30
Build Status:  Still Failing
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #1
No changes

Changes for Build #2
[Gal Ben Haim] 4.2: Backport tests from master


Changes for Build #3
[Gal Ben Haim] 4.2: Backport tests from master

[Sandro Bonazzola] guest agent: move to fc28

[Martin Perina] ovirt-engine: Drop FC28 build from 4.2

[arachmani] ovirt-engine-api-explorer: move from fc27 to fc 28


Changes for Build #4
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs

[arachmani] ovirt-dwh: Move from fc27 to fc28

[arachmani] ovirt-hosted-engine-ha: Move to fc28 and exclude 4.2 on fc28

[arachmani] ovirt-engine-metrics: Move to fc28 and exclude 4.2 on fc28

[arachmani] cockpit-ovirt: Move to fc28 and exclude 4.2 on fc28


Changes for Build #5
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs


Changes for Build #6
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs

[Sandro Bonazzola] ovirt-engine: exclude fc28 on 4.2.3 branch

[Sandro Bonazzola] ovirt-release: switch to fc28


Changes for Build #7
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs

[Gal Ben Haim] OST: pin HC suites to "ovirt-srv05.phx.ovirt.org"


Changes for Build #8
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs


Changes for Build #9
[Dominik Holler] reflect package python-netaddr rename to python2-netaddr


Changes for Build #10
[Dominik Holler] network: use neutron compatible IP addresses

[Ondra Machacek] sdk: Update to fedora 28


Changes for Build #11
[Gal Ben Haim] Adjust SSH timeout exception


Changes for Build #12
[Gal Ben Haim] Remove 4.1 suites automation files


Changes for Build #13
[Gal Ben Haim] Remove 4.1 suites automation files

[Daniel Belenky] DSL: Do not normalize release_branches values

[Sandro Bonazzola] javascript: move to fc28


Changes for Build #14
[Gal Ben Haim] Remove 4.1 suites automation files


Changes for Build #15
[Gal Ben Haim] Remove 4.1 suites automation files

[Sandro Bonazzola] vdsm-jsonrpc-java: switch to fc28

[Sandro Bonazzola] nsis: switch to fc28


Changes for Build #16
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing

[Sandro Bonazzola] dashboard: don't build fc28 for 4.2

[Sandro Bonazzola] mom: switch to fc28

[Sandro Bonazzola] ovirt-vmconsole: switch to fc28

[Sandro Bonazzola] ioprocess: switch to fc28

[Sandro Bonazzola] ovirt-provider-ovn: switch to fc28

[Sandro Bonazzola] log-collector: switch to fc28


Changes for Build #17
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #18
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #19
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #20
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #21
[Yuval Turgeman] node-ng: add python-ovirt-engine-sdk4 to reposync


Changes for Build #22
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #23
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #24
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #25
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #26
[Marcin Mirecki] network: add test validating connections between OVN  networks


Changes for Build #27
[Marcin Mirecki] network: add test validating connections between OVN  networks


Changes for Build #28
[Andrej Krejcir] HE: Test restarting HE VM


Changes for Build #29
[Andrej Krejcir] HE: Test restarting HE VM


Changes for Build #30
[Andrej Krejcir] HE: Test restarting HE VM




-
Failed Tests:
-
No tests ran.___
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/I3FFPXPXJZXW4HSVK5O2T7PO33NFCBJO/

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 474 - Failure!

[jenkins]

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/474/
Build Number: 474
Build Status:  Failure
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #474
[Andrej Krejcir] HE: Test restarting HE VM




-
Failed Tests:
-
No tests ran.___
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/PIGSZ4L56VF4EFIXOJSH6ME43M2B5K5M/

[CQ]: 92142,2 (ovirt-engine) failed "ovirt-master" system tests

[oVirt Jenkins]

Change 92142,2 (ovirt-engine) is probably the reason behind recent system test
failures in the "ovirt-master" change queue and needs to be fixed.

This change had been removed from the testing queue. Artifacts build from this
change will not be released until it is fixed.

For further details about the change see:
https://gerrit.ovirt.org/#/c/92142/2

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8178/
___
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/RK5AQJBDUHD6TJZ2X7UIA3CMF5PKKTDK/

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 95 - Still Failing!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/95/
Build Number: 95
Build Status:  Still Failing
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #68
[Gal Ben Haim] 4.2: Backport tests from master

[Barak Korren] Fix mock_cleanup.sh trying to umount bad things

[Barak Korren] Switch fabric-ovirt to STDCI v2


Changes for Build #69
[Gal Ben Haim] 4.2: Backport tests from master


Changes for Build #70
[Gal Ben Haim] 4.2: Backport tests from master

[Sandro Bonazzola] guest agent: move to fc28

[Martin Perina] ovirt-engine: Drop FC28 build from 4.2

[arachmani] ovirt-engine-api-explorer: move from fc27 to fc 28

[arachmani] ovirt-dwh: Move from fc27 to fc28

[arachmani] ovirt-hosted-engine-ha: Move to fc28 and exclude 4.2 on fc28


Changes for Build #71
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs

[arachmani] ovirt-engine-metrics: Move to fc28 and exclude 4.2 on fc28

[arachmani] cockpit-ovirt: Move to fc28 and exclude 4.2 on fc28


Changes for Build #72
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs


Changes for Build #73
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs

[Sandro Bonazzola] ovirt-engine: exclude fc28 on 4.2.3 branch

[Sandro Bonazzola] ovirt-release: switch to fc28

[Gal Ben Haim] OST: pin HC suites to "ovirt-srv05.phx.ovirt.org"


Changes for Build #74
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs


Changes for Build #75
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs


Changes for Build #76
[Dominik Holler] network: use neutron compatible IP addresses


Changes for Build #77
[Gal Ben Haim] Adjust SSH timeout exception

[Ondra Machacek] sdk: Update to fedora 28


Changes for Build #78
[Gal Ben Haim] Adjust SSH timeout exception


Changes for Build #79
[Gal Ben Haim] Remove 4.1 suites automation files

[Daniel Belenky] DSL: Do not normalize release_branches values


Changes for Build #80
[Gal Ben Haim] Remove 4.1 suites automation files

[Sandro Bonazzola] javascript: move to fc28


Changes for Build #81
[Gal Ben Haim] Remove 4.1 suites automation files


Changes for Build #82
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing

[Sandro Bonazzola] vdsm-jsonrpc-java: switch to fc28

[Sandro Bonazzola] nsis: switch to fc28

[Sandro Bonazzola] dashboard: don't build fc28 for 4.2

[Sandro Bonazzola] mom: switch to fc28

[Sandro Bonazzola] ovirt-vmconsole: switch to fc28


Changes for Build #83
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing

[Sandro Bonazzola] ioprocess: switch to fc28

[Sandro Bonazzola] ovirt-provider-ovn: switch to fc28

[Sandro Bonazzola] log-collector: switch to fc28


Changes for Build #84
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #85
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #86
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #87
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #88
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #89
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #90
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #91
[Marcin Mirecki] network: add test validating connections between OVN  networks


Changes for Build #92
[Marcin Mirecki] network: add test validating connections between OVN  networks


Changes for Build #93
[Marcin Mirecki] network: add test validating connections between OVN  networks


Changes for Build #94
[Andrej Krejcir] HE: Test restarting HE VM


Changes for Build #95
[Andrej Krejcir] HE: Test restarting HE VM




-
Failed Tests:
-
No tests ran.___
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/XTYLJPN7474P5NJDI7Y5QLLWJRSAJU4W/

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 237 - Failure!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/237/
Build Number: 237
Build Status:  Failure
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #237
[Andrej Krejcir] HE: Test restarting HE VM




-
Failed Tests:
-
All tests passed___
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/U7C3BRRAWX5XXDSGHQWFQMABUEURKRZC/

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 29 - Fixed!

[jenkins]

Project: 
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/29/
Build Number: 29
Build Status:  Fixed
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #28
[Andrej Krejcir] HE: Test restarting HE VM


Changes for Build #29
[Andrej Krejcir] HE: Test restarting HE VM




-
Failed Tests:
-
All tests passed___
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/NTUJNTDUP7445Y6OHRFGPIWZK6JDFHGK/

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 255 - Failure!

[jenkins]

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ 
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/255/
Build Number: 255
Build Status:  Failure
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #255
[Andrej Krejcir] HE: Test restarting HE VM




-
Failed Tests:
-
No tests ran.___
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/RCYN6TEI7TEKFHXZNJFZGNENS3ZZ73WG/

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-4.2 - Build # 29 - Still Failing!

[jenkins]

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/ 
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-4.2/29/
Build Number: 29
Build Status:  Still Failing
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #1
No changes

Changes for Build #2
[Gal Ben Haim] 4.2: Backport tests from master


Changes for Build #3
[Gal Ben Haim] 4.2: Backport tests from master

[Sandro Bonazzola] guest agent: move to fc28

[Martin Perina] ovirt-engine: Drop FC28 build from 4.2

[arachmani] ovirt-engine-api-explorer: move from fc27 to fc 28


Changes for Build #4
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs

[arachmani] ovirt-dwh: Move from fc27 to fc28

[arachmani] ovirt-hosted-engine-ha: Move to fc28 and exclude 4.2 on fc28

[arachmani] ovirt-engine-metrics: Move to fc28 and exclude 4.2 on fc28

[arachmani] cockpit-ovirt: Move to fc28 and exclude 4.2 on fc28


Changes for Build #5
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs


Changes for Build #6
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs

[Sandro Bonazzola] ovirt-engine: exclude fc28 on 4.2.3 branch

[Sandro Bonazzola] ovirt-release: switch to fc28


Changes for Build #7
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs

[Gal Ben Haim] OST: pin HC suites to "ovirt-srv05.phx.ovirt.org"


Changes for Build #8
[Eyal Edri] Refresh ovirt-master reposync with latest pkgs


Changes for Build #9
[Dominik Holler] reflect package python-netaddr rename to python2-netaddr


Changes for Build #10
[Dominik Holler] network: use neutron compatible IP addresses

[Ondra Machacek] sdk: Update to fedora 28


Changes for Build #11
[Gal Ben Haim] Adjust SSH timeout exception


Changes for Build #12
[Gal Ben Haim] Remove 4.1 suites automation files


Changes for Build #13
[Gal Ben Haim] Remove 4.1 suites automation files

[Daniel Belenky] DSL: Do not normalize release_branches values

[Sandro Bonazzola] javascript: move to fc28


Changes for Build #14
[Gal Ben Haim] Remove 4.1 suites automation files


Changes for Build #15
[Gal Ben Haim] Remove 4.1 suites automation files

[Sandro Bonazzola] vdsm-jsonrpc-java: switch to fc28

[Sandro Bonazzola] nsis: switch to fc28


Changes for Build #16
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing

[Sandro Bonazzola] dashboard: don't build fc28 for 4.2

[Sandro Bonazzola] mom: switch to fc28

[Sandro Bonazzola] ovirt-vmconsole: switch to fc28

[Sandro Bonazzola] ioprocess: switch to fc28

[Sandro Bonazzola] ovirt-provider-ovn: switch to fc28

[Sandro Bonazzola] log-collector: switch to fc28


Changes for Build #17
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #18
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #19
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #20
[Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing


Changes for Build #21
[Yuval Turgeman] node-ng: add python-ovirt-engine-sdk4 to reposync


Changes for Build #22
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #23
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #24
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #25
[Eitan Raviv] network: introduce wait for 'powering up' or 'up'


Changes for Build #26
[Marcin Mirecki] network: add test validating connections between OVN  networks


Changes for Build #27
[Marcin Mirecki] network: add test validating connections between OVN  networks


Changes for Build #28
[Andrej Krejcir] HE: Test restarting HE VM


Changes for Build #29
[Andrej Krejcir] HE: Test restarting HE VM




-
Failed Tests:
-
No tests ran.___
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/MAEWXNRAHI33KNOEGA62Q2I557244JJD/

Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 05-06-2018 ] [ 002_bootstrap.update_default_cluster ]

[Eli Mesika]

Patch on master merged , patch on 4.2 is waiting for CI and then will be
merged

On Tue, Jun 12, 2018 at 1:00 PM, Dafna Ron  wrote:

> Hi Martin, Eli and Arik.
>
> can you please give an update on this?
>
> Is there a bug reported for this?
>
> Thanks,
> Danfa
>
>
> On Fri, Jun 8, 2018 at 1:26 PM, Martin Perina  wrote:
>
>>
>>
>> On Fri, Jun 8, 2018 at 12:56 PM, Dafna Ron  wrote:
>>
>>> Hi Martin, Eli,
>>>
>>> It seems the fix has failed on the same test:
>>> https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovi
>>> rt-master_change-queue-tester/8068/
>>>
>>> can you please have a look?
>>>
>>
>> ​It's strange, because Eli manually verified upgrade OST for master and
>> it worked.
>>
>> But yeah, we know that provided fix didn't solve all cpu_name related
>> issues and Eli is working on complete fix with Arik:
>> https://gerrit.ovirt.org/#/c/92049/
>> Eli, please try to put maximum priority on it during Sunday and merge the
>> fix if acked by Arik.
>> ​
>> Thanks
>>
>> Martin
>>
>>
>>> Thanks,
>>> Dafna
>>>
>>>
>>> On Wed, Jun 6, 2018 at 11:03 AM, Dafna Ron  wrote:
>>>
 Thanks Eli.

 On Wed, Jun 6, 2018 at 10:49 AM, Eli Mesika  wrote:

> Hi Dafna
>
> We are aware of that, the patch will be merged upstream ASAP and I
> sent a 4.2 patch as well , hope to have both merge soon
>
> On Wed, Jun 6, 2018 at 11:45 AM, Dafna Ron  wrote:
>
>> any idea when the fix will be merged? for now, ovirt-engine is
>> broken.
>>
>> On Tue, Jun 5, 2018 at 9:37 PM, Eli Mesika 
>> wrote:
>>
>>> Yes I do
>>>
>>> On Tue, Jun 5, 2018 at 7:20 PM, Martin Perina 
>>> wrote:
>>>


 On Tue, Jun 5, 2018 at 5:08 PM, Dafna Ron  wrote:

> Eli, Martin,
> Any updates?
>

 ​Eli, do you think that https://gerrit.ovirt.org/91968​ fixes also
 this OST failure?


>
> On Tue, Jun 5, 2018 at 12:15 PM, Dafna Ron 
> wrote:
>
>>
>>
>>
>>
>> *Hi, We have a failure in ovirt-engine on master on update
>> cluster because of "cpu not found" CQ reported the below as the most
>> possible cause for the failure. I looked at the other changes that 
>> ran and
>> I don't think any of them would be the cause of failure. *
>>
>>
>>
>> *Can you please have a look at this issue? *
>>
>>
>> *Link and headline of suspected patches: *
>>
>> https://gerrit.ovirt.org/#/c/91888/ - db:fix upgrade issue on
>> NULL values
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Link to
>> Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8033/
>> Link
>> to all
>> logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8033/artifact/exported-artifacts/basic-suit-master-el7/test_logs/basic-suite-master/post-002_bootstrap.py/
>> (Relevant)
>> error snippet from the log: 2018-06-04 11:56:31,958-04 INFO
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (default task-13) [] EVENT_ID: USER_ADDED_CPU_PROFILE(10,130), CPU 
>> Profile
>> test-cluster was successfully added (User: 
>> admin@internal-authz).2018-06-04
>> 11:56:31,959-04 DEBUG
>> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
>> (default task-13) [] method: runAction, params: [AddCpuProfile,
>> CpuProfileParameters:{commandId='c76f8e59-c9a2-4601-964e-a92e9cb668ce',
>>  user='admin',
>> commandType='Unknown'}], timeElapsed: 168ms2018-06-04 
>> 11:56:31,974-04 INFO
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (default task-13) [] EVENT_ID: USER_ADD_CLUSTER(809), Cluster 
>> test-cluster
>> was added by admin@internal-authz2018-06-04 11:56:31,975-04 DEBUG
>> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
>> (default task-13) [] method: runAction, params: [AddCluster,
>> ManagementNetworkOnClusterOperationParameters:{commandId='3e0bf24c-4c49-4094-928d-7c15ef50ff62',
>> user='null', commandType='Unknown'}], timeElapsed: 272ms2018-06-04
>> 11:56:31,980-04 DEBUG
>> [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
>> (default task-13) [8ef59a69-020e-407c-9766-fbd3a6cc9381] method: 
>> runQuery,
>

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 473 - Fixed!

[jenkins]

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ 
Build: 
http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/473/
Build Number: 473
Build Status:  Fixed
Triggered By: Started by timer

-
Changes Since Last Success:
-
Changes for Build #472
[Marcin Mirecki] network: add test validating connections between OVN  networks


Changes for Build #473
[Andrej Krejcir] HE: Test restarting HE VM




-
Failed Tests:
-
All tests passed___
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/CNKTB5TD74X2QTLPWBH7H275MJ7ZUJRT/

Change in stdci-staging[master]: Add stuff to test other stuff

[review]

>From Evgheni Dereveanchin :

Evgheni Dereveanchin has uploaded a new patch set (#2) to the change originally 
created by Daniel Belenky. ( https://gerrit-staging.phx.ovirt.org/156 )

Change subject: Add stuff to test other stuff
..

Add stuff to test other stuff

Change-Id: If5c1f99a7cda70ee12576d6d482d81206e274a55
Signed-off-by: Daniel Belenky 
---
A automation/check-patch.another-failed.sh
A automation/check-patch.failed.sh
M automation/check-patch.sh
A stdci.yaml
4 files changed, 10 insertions(+), 0 deletions(-)


  git pull ssh://gerrit-staging.phx.ovirt.org:29418/stdci-staging 
refs/changes/56/156/2
--
To view, visit https://gerrit-staging.phx.ovirt.org/156
To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings

Gerrit-Project: stdci-staging
Gerrit-Branch: master
Gerrit-MessageType: newpatchset
Gerrit-Change-Id: If5c1f99a7cda70ee12576d6d482d81206e274a55
Gerrit-Change-Number: 156
Gerrit-PatchSet: 2
Gerrit-Owner: Daniel Belenky 
Gerrit-Reviewer: Daniel Belenky 
Gerrit-Reviewer: Jenkins CI 
___
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/7HCUJFAO7XMAVRWRC3TD7P3EXOHQC3WJ/

[JIRA] (OVIRT-1113) Automate project Gerrit repo creation

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1113:
-
Labels: Icebox first_time_task  (was: first_time_task)

> Automate project Gerrit repo creation
> -
>
> Key: OVIRT-1113
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1113
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Gerrit/git
>Reporter: Barak Korren
>Assignee: infra
>Priority: Low
>  Labels: Icebox, first_time_task
>
> Because the doc is annoying to follow manually, and its easy to automate 
> Gerrit, the API is basically 'ssh'.
> Long term if the automation is good we could make this "self service".



--
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/3HGQCLZ5RMX5R4ANA2VRC33DJHYQKAY2/

[JIRA] (OVIRT-1113) Automate project Gerrit repo creation

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1113:
-
Epic Link:   (was: OVIRT-403)

> Automate project Gerrit repo creation
> -
>
> Key: OVIRT-1113
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1113
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Gerrit/git
>Reporter: Barak Korren
>Assignee: infra
>Priority: Low
>  Labels: first_time_task
>
> Because the doc is annoying to follow manually, and its easy to automate 
> Gerrit, the API is basically 'ssh'.
> Long term if the automation is good we could make this "self service".



--
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/GSIZWWE7KFII7H25I7QCANVCP6RRENCU/

[JIRA] (OVIRT-1113) Automate project Gerrit repo creation

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1113:
-
Epic Link: (was: OVIRT-403)

> Automate project Gerrit repo creation
> -
>
> Key: OVIRT-1113
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1113
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Gerrit/git
>Reporter: Barak Korren
>Assignee: infra
>Priority: Low
>  Labels: first_time_task
>
> Because the doc is annoying to follow manually, and its easy to automate 
> Gerrit, the API is basically 'ssh'.
> Long term if the automation is good we could make this "self service".



--
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/VZSKNZ62E3QFHQ5O4S7HWN3L4KEZ/

[JIRA] (OVIRT-1139) Remove 'github plugin' loggers in jenkins

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1139:
-
Resolution: Won't Do
Status: Done  (was: To Do)

> Remove 'github plugin' loggers in jenkins
> -
>
> Key: OVIRT-1139
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1139
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Nadav Goldin
>Assignee: infra
>
> Just a reminder to disable the GitHub plugin loggers setup at:
> http://jenkins.ovirt.org/log/
> After:
> https://ovirt-jira.atlassian.net/browse/OVIRT-1138
> https://ovirt-jira.atlassian.net/browse/OVIRT-874
> Are resolved.



--
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/QVGWZPFTQ6CQ6AM7PTMUBDRU5I3CKNB6/

[JIRA] (OVIRT-1139) Remove 'github plugin' loggers in jenkins

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1139:
-
Epic Link:   (was: OVIRT-403)

> Remove 'github plugin' loggers in jenkins
> -
>
> Key: OVIRT-1139
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1139
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Nadav Goldin
>Assignee: infra
>
> Just a reminder to disable the GitHub plugin loggers setup at:
> http://jenkins.ovirt.org/log/
> After:
> https://ovirt-jira.atlassian.net/browse/OVIRT-1138
> https://ovirt-jira.atlassian.net/browse/OVIRT-874
> Are resolved.



--
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/GR2E4CG5EGC6TCI5OPR2JJL2JPO3VGVC/

[JIRA] (OVIRT-1139) Remove 'github plugin' loggers in jenkins

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1139:
-
Epic Link: (was: OVIRT-403)

> Remove 'github plugin' loggers in jenkins
> -
>
> Key: OVIRT-1139
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1139
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Nadav Goldin
>Assignee: infra
>
> Just a reminder to disable the GitHub plugin loggers setup at:
> http://jenkins.ovirt.org/log/
> After:
> https://ovirt-jira.atlassian.net/browse/OVIRT-1138
> https://ovirt-jira.atlassian.net/browse/OVIRT-874
> Are resolved.



--
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/CZXEW5LABGKE2JPLMGYSY5QC7QHUP6DU/

[JIRA] (OVIRT-1495) Check out Gerrit metrics feature to see if we can push stats to graphana

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1495:
-
Epic Link: (was: OVIRT-403)

> Check out Gerrit metrics feature to see if we can push stats to graphana
> 
>
> Key: OVIRT-1495
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1495
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eyal edri
>Assignee: infra
>
> Gerrit 2.13 added a new feature that allows sending metrics to an external 
> source like Graphite.
> It would be interesting to see if we can push status about our Gerrit 
> instance to our Graphana instance.
> More info at:
> https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html
> https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html



--
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/72JZALBYSSWCLNFAHR4GHYQZAMCV5SZ7/

[JIRA] (OVIRT-1231) Security: do we need HSTS for oVirt services?

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1231:
-
Resolution: Fixed
Status: Done  (was: To Do)

HSTS already enabled for oVirt services

> Security: do we need HSTS for oVirt services?
> -
>
> Key: OVIRT-1231
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1231
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: eyal edri
>Assignee: infra
>
> https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
> Most of the browsers already supports it and some websites started to enforce 
> it.
> cc [~dfediuck]



--
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/RHEIB2XAK67Z3MD5K2THULVKHFKQAGE3/

[JIRA] (OVIRT-1231) Security: do we need HSTS for oVirt services?

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1231:
-
Epic Link:   (was: OVIRT-403)

> Security: do we need HSTS for oVirt services?
> -
>
> Key: OVIRT-1231
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1231
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: eyal edri
>Assignee: infra
>
> https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
> Most of the browsers already supports it and some websites started to enforce 
> it.
> cc [~dfediuck]



--
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/YNW4T5BNLCJJWYDUZ2N6GD2JCVQAW2W6/

[JIRA] (OVIRT-1231) Security: do we need HSTS for oVirt services?

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1231:
-
Epic Link: (was: OVIRT-403)

> Security: do we need HSTS for oVirt services?
> -
>
> Key: OVIRT-1231
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1231
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: eyal edri
>Assignee: infra
>
> https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
> Most of the browsers already supports it and some websites started to enforce 
> it.
> cc [~dfediuck]



--
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/QXNSMU4INWSXMXZ6K4HTZJ3SOBMFF5VT/

[JIRA] (OVIRT-1495) Check out Gerrit metrics feature to see if we can push stats to graphana

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri reassigned OVIRT-1495:


Assignee: Evgheni Dereveanchin  (was: infra)

> Check out Gerrit metrics feature to see if we can push stats to graphana
> 
>
> Key: OVIRT-1495
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1495
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Gerrit/git
>Reporter: eyal edri
>Assignee: Evgheni Dereveanchin
>  Labels: monitoring,
>
> Gerrit 2.13 added a new feature that allows sending metrics to an external 
> source like Graphite.
> It would be interesting to see if we can push status about our Gerrit 
> instance to our Graphana instance.
> More info at:
> https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html
> https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html



--
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/QF4XMGSPKKBMT3VCTKJRE7RFKR6VJ6TP/

[JIRA] (OVIRT-1495) Check out Gerrit metrics feature to see if we can push stats to graphana

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1495:
-
Component/s: Gerrit/git

> Check out Gerrit metrics feature to see if we can push stats to graphana
> 
>
> Key: OVIRT-1495
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1495
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Gerrit/git
>Reporter: eyal edri
>Assignee: infra
>
> Gerrit 2.13 added a new feature that allows sending metrics to an external 
> source like Graphite.
> It would be interesting to see if we can push status about our Gerrit 
> instance to our Graphana instance.
> More info at:
> https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html
> https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html



--
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/NDO4RHWJWTVZGLVQ5DB6VEZDANBZMWOZ/

[JIRA] (OVIRT-1495) Check out Gerrit metrics feature to see if we can push stats to graphana

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1495:
-
Epic Link:   (was: OVIRT-403)

> Check out Gerrit metrics feature to see if we can push stats to graphana
> 
>
> Key: OVIRT-1495
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1495
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: eyal edri
>Assignee: infra
>
> Gerrit 2.13 added a new feature that allows sending metrics to an external 
> source like Graphite.
> It would be interesting to see if we can push status about our Gerrit 
> instance to our Graphana instance.
> More info at:
> https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html
> https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html



--
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/ZPYFMXI77OUGIVZYBUDFWM3OEOH5CKM3/

[JIRA] (OVIRT-1495) Check out Gerrit metrics feature to see if we can push stats to graphana

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1495:
-
Labels: monitoring,  (was: )

> Check out Gerrit metrics feature to see if we can push stats to graphana
> 
>
> Key: OVIRT-1495
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1495
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Gerrit/git
>Reporter: eyal edri
>Assignee: infra
>  Labels: monitoring,
>
> Gerrit 2.13 added a new feature that allows sending metrics to an external 
> source like Graphite.
> It would be interesting to see if we can push status about our Gerrit 
> instance to our Graphana instance.
> More info at:
> https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html
> https://gerrit-documentation.storage.googleapis.com/Documentation/2.13/metrics.html



--
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/KLTD443GARUPJIPXXT3LLPXETS6M2XTL/

[JIRA] (OVIRT-1866) Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1866:

Epic Link:   (was: OVIRT-400)

> Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY
> 
>
> Key: OVIRT-1866
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins Master
>Reporter: Daniel Belenky
>Assignee: infra
>  Labels: jenkins
>
> It seems that pipelines now have support to configure their behavior of 
> serialization of objects, and since we know that this serialization never 
> worked for us as we'd expect it to, maybe we should consider using 
> PERFORMANCE_OPTIMIZED mode which will avoid serializing and maybe boost the 
> performance.
> [Link to subject in jenkincci-dev 
> google|https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51qixjepCgAJ]



--
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/MP3J5QF7X3VTHLUMECRPO6XNHH2UMLS5/

[JIRA] (OVIRT-1867) Allow embedded secrets inside the source repo for CI

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1867:

Epic Link:   (was: OVIRT-400)

> Allow embedded secrets inside the source repo for CI
> 
>
> Key: OVIRT-1867
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1867
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Standard CI (Pipelines), STDCI DSL
>Reporter: Roman Mohr
>Assignee: infra
>  Labels: credentials
>
> In order to improve the self-service capabilities of standard-ci it is
> important for projects, that they can add their own secrets to projects (to
> reach external services, e.g. docker hub, ...).
> Travis has a very nice system which helps engineers there:
> https://docs.travis-ci.com/user/encryption-keys/
> Basically the CI system needs to generate a public/private key pair for
> every enabled git repo. The engineer simply fetches the public key via a
> well know URL and encrypts the secrets. Then the encrypted secret can be
> made part of the source repo. Before the tests are run the CI system
> decrypts the secrets. Than can play together pretty well with Jenkinsfiles
> too.
> Benefit:
>  * Less manual intervention from CI team to add secrets to jobs
>  * Strengthen the config-in-code thinking



--
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/GYN4FX5JCBC34DZTNV6WWHLOKLV2GKHP/

[JIRA] (OVIRT-1867) Allow embedded secrets inside the source repo for CI

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1867:

Epic Link: (was: OVIRT-400)

> Allow embedded secrets inside the source repo for CI
> 
>
> Key: OVIRT-1867
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1867
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Standard CI (Pipelines), STDCI DSL
>Reporter: Roman Mohr
>Assignee: infra
>  Labels: credentials
>
> In order to improve the self-service capabilities of standard-ci it is
> important for projects, that they can add their own secrets to projects (to
> reach external services, e.g. docker hub, ...).
> Travis has a very nice system which helps engineers there:
> https://docs.travis-ci.com/user/encryption-keys/
> Basically the CI system needs to generate a public/private key pair for
> every enabled git repo. The engineer simply fetches the public key via a
> well know URL and encrypts the secrets. Then the encrypted secret can be
> made part of the source repo. Before the tests are run the CI system
> decrypts the secrets. Than can play together pretty well with Jenkinsfiles
> too.
> Benefit:
>  * Less manual intervention from CI team to add secrets to jobs
>  * Strengthen the config-in-code thinking



--
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/XCMSHYSTVDIPFOEZXLOY5K4KSZMCZBAI/

[JIRA] (OVIRT-1866) Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1866:

Epic Link: (was: OVIRT-400)

> Use PERFORMANCE_OPTIMIZED pipelines instead of MAX_SURVIVABILITY
> 
>
> Key: OVIRT-1866
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1866
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins Master
>Reporter: Daniel Belenky
>Assignee: infra
>  Labels: jenkins
>
> It seems that pipelines now have support to configure their behavior of 
> serialization of objects, and since we know that this serialization never 
> worked for us as we'd expect it to, maybe we should consider using 
> PERFORMANCE_OPTIMIZED mode which will avoid serializing and maybe boost the 
> performance.
> [Link to subject in jenkincci-dev 
> google|https://groups.google.com/forum/#!msg/jenkinsci-dev/F4zcOWLI32w/51qixjepCgAJ]



--
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/PDXQKQAW5GQ3UFWKSWK74H2LYGPL7TUV/

[JIRA] (OVIRT-1874) Manual building UI

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1874:

Summary: Manual building UI  (was: Manual building)

> Manual building UI
> --
>
> Key: OVIRT-1874
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1874
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Standard CI (Pipelines)
>Reporter: Lev Veyde
>Assignee: infra
>  Labels: builds, releases
>
> Hi,
> We need the interface to be able to do manual builds from specific refs
> (i.e. tag/hash) for the projects.
> Thanks,
> -- 
> Lev Veyde
> Software Engineer, RHCE | RHCVA | MCITP
> Red Hat Israel
> 
> l...@redhat.com | lve...@redhat.com
> 
> TRIED. TESTED. TRUSTED. 



--
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/TNW4PBIDCZVLZ2XN22YBHSKMZLW65OQG/

[JIRA] (OVIRT-1868) Allow engineers to write Jenkinsfiles

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1868:

Epic Link:   (was: OVIRT-400)

> Allow engineers to write Jenkinsfiles
> -
>
> Key: OVIRT-1868
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1868
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Standard CI (Pipelines)
>Reporter: Roman Mohr
>Assignee: infra
>
> Looks like standard-ci switched internally to use Jenkinsfiles. However it
> would be very valuable for engineers, if they could just write their
> Jenkinsfile, instead of all the usual standard-ci yamls/scripts.
> With the Jenkinsfile the chroot based approach seems to be pretty obsolete,
> if you allow people to use the docker agent for the Jenkinsfile. For
> KubeVirt it would make standard-ci finally really valuable.



--
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/UZO54GKE2CPNE63N7KKV6GMSFRSZKFQV/

[JIRA] (OVIRT-1868) Allow engineers to write Jenkinsfiles

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1868:

Epic Link: (was: OVIRT-400)

> Allow engineers to write Jenkinsfiles
> -
>
> Key: OVIRT-1868
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1868
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Standard CI (Pipelines)
>Reporter: Roman Mohr
>Assignee: infra
>
> Looks like standard-ci switched internally to use Jenkinsfiles. However it
> would be very valuable for engineers, if they could just write their
> Jenkinsfile, instead of all the usual standard-ci yamls/scripts.
> With the Jenkinsfile the chroot based approach seems to be pretty obsolete,
> if you allow people to use the docker agent for the Jenkinsfile. For
> KubeVirt it would make standard-ci finally really valuable.



--
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/CFMLJIQZ6HDTV3HSS4BBDYHBO25W2WNH/

[JIRA] (OVIRT-1874) Manual building

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1874:

Epic Link: (was: OVIRT-400)

> Manual building
> ---
>
> Key: OVIRT-1874
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1874
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Standard CI (Pipelines)
>Reporter: Lev Veyde
>Assignee: infra
>  Labels: builds, releases
>
> Hi,
> We need the interface to be able to do manual builds from specific refs
> (i.e. tag/hash) for the projects.
> Thanks,
> -- 
> Lev Veyde
> Software Engineer, RHCE | RHCVA | MCITP
> Red Hat Israel
> 
> l...@redhat.com | lve...@redhat.com
> 
> TRIED. TESTED. TRUSTED. 



--
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/HD5EV7OA7EYDLOLGN6P6AHL5LFAMEFW7/

[JIRA] (OVIRT-1874) Manual building

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1874:

Epic Link:   (was: OVIRT-400)

> Manual building
> ---
>
> Key: OVIRT-1874
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1874
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Standard CI (Pipelines)
>Reporter: Lev Veyde
>Assignee: infra
>  Labels: builds, releases
>
> Hi,
> We need the interface to be able to do manual builds from specific refs
> (i.e. tag/hash) for the projects.
> Thanks,
> -- 
> Lev Veyde
> Software Engineer, RHCE | RHCVA | MCITP
> Red Hat Israel
> 
> l...@redhat.com | lve...@redhat.com
> 
> TRIED. TESTED. TRUSTED. 



--
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/A4J3DNBDG5HK4S43KAUEGECGMXVGS4AU/

[JIRA] (OVIRT-1767) Look into replacing gitweb for oVirt Gerrit

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1767:
-
Epic Link: (was: OVIRT-403)

> Look into replacing gitweb for oVirt Gerrit
> ---
>
> Key: OVIRT-1767
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Gerrit/git
>Reporter: Barak Korren
>Assignee: infra
>Priority: Low
>  Labels: Icebox, gerrit
>
> One of the faults of our Gerrit system is that the source browser look like 
> it belongs to a different century.
> There seems to be a Gerrit plugin which allows using Gitiles rather then 
> gitweb in Gerrit:
> https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gitiles
> Gitiles itself seems to be a more modern Git UI then gitweb, at the very 
> least is supports showing markdown files, which is a staple of modern source 
> browsers:
> https://gerrit.googlesource.com/gitiles/
> Another plugin to consider is the one for using GitBlit:
> https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gitblit
> Gitblit is another Java based Gir bowser:
> http://gitblit.com/features.html



--
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/ZQ7AR7BMJXMZTFK4H3KH7I64GGR57ULS/

[JIRA] (OVIRT-1767) Look into replacing gitweb for oVirt Gerrit

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1767:
-
Epic Link:   (was: OVIRT-403)

> Look into replacing gitweb for oVirt Gerrit
> ---
>
> Key: OVIRT-1767
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Gerrit/git
>Reporter: Barak Korren
>Assignee: infra
>Priority: Low
>  Labels: Icebox, gerrit
>
> One of the faults of our Gerrit system is that the source browser look like 
> it belongs to a different century.
> There seems to be a Gerrit plugin which allows using Gitiles rather then 
> gitweb in Gerrit:
> https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gitiles
> Gitiles itself seems to be a more modern Git UI then gitweb, at the very 
> least is supports showing markdown files, which is a staple of modern source 
> browsers:
> https://gerrit.googlesource.com/gitiles/
> Another plugin to consider is the one for using GitBlit:
> https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gitblit
> Gitblit is another Java based Gir bowser:
> http://gitblit.com/features.html



--
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/5QCXUTME54WGD6SOIWE7OCZSUMZ7WOTP/

[JIRA] (OVIRT-1318) configure backup of status.ovirt.org

[Evgheni Dereveanchin (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Evgheni Dereveanchin updated OVIRT-1318:

Epic Link: OVIRT-2194  (was: OVIRT-403)

> configure backup of status.ovirt.org
> 
>
> Key: OVIRT-1318
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1318
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Evgheni Dereveanchin
>Assignee: infra
>Priority: Low
>
> status.ovirt.org was set up - need to investigate if it needs to be backed up 
> or we can produce documentation to set up a new stats page in case something 
> happens to the existing OpenShift gear.
> We can use OpenShift's built in backup/restore functionality:
> https://developers.openshift.com/managing-your-applications/backing-up-applications.html



--
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/D5PXISULVUCX5XL627WRENKUJSEOHRBB/

[JIRA] (OVIRT-1318) configure backup of status.ovirt.org

[Evgheni Dereveanchin (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Evgheni Dereveanchin updated OVIRT-1318:

Epic Link: OVIRT-2194  (was: OVIRT-403)

> configure backup of status.ovirt.org
> 
>
> Key: OVIRT-1318
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1318
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Evgheni Dereveanchin
>Assignee: infra
>Priority: Low
>
> status.ovirt.org was set up - need to investigate if it needs to be backed up 
> or we can produce documentation to set up a new stats page in case something 
> happens to the existing OpenShift gear.
> We can use OpenShift's built in backup/restore functionality:
> https://developers.openshift.com/managing-your-applications/backing-up-applications.html



--
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/QM6R4UTHIOKGFNTSZRG36QANOWF6MC4Q/

[JIRA] (OVIRT-1767) Look into replacing gitweb for oVirt Gerrit

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1767:
-
Labels: Icebox gerrit  (was: gerrit)

> Look into replacing gitweb for oVirt Gerrit
> ---
>
> Key: OVIRT-1767
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Gerrit/git
>Reporter: Barak Korren
>Assignee: infra
>Priority: Low
>  Labels: Icebox, gerrit
>
> One of the faults of our Gerrit system is that the source browser look like 
> it belongs to a different century.
> There seems to be a Gerrit plugin which allows using Gitiles rather then 
> gitweb in Gerrit:
> https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gitiles
> Gitiles itself seems to be a more modern Git UI then gitweb, at the very 
> least is supports showing markdown files, which is a staple of modern source 
> browsers:
> https://gerrit.googlesource.com/gitiles/
> Another plugin to consider is the one for using GitBlit:
> https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gitblit
> Gitblit is another Java based Gir bowser:
> http://gitblit.com/features.html



--
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/SSQXWITMWS4JNTW3INC7XQ5HNT5S5LSX/

[JIRA] (OVIRT-1319) configure backup of stats.phx.ovirt.org

[Evgheni Dereveanchin (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Evgheni Dereveanchin updated OVIRT-1319:

Epic Link: OVIRT-2194

> configure backup of stats.phx.ovirt.org
> ---
>
> Key: OVIRT-1319
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1319
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Evgheni Dereveanchin
>Assignee: infra
>Priority: Low
>  Labels: backup, phx
>
> The stats server is accumulating historical data, backups need to be set up 
> so that we don't risk losing it.



--
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/PB5H522EOONBDHUZ7WN6OLE64MLT2FRT/

[JIRA] (OVIRT-1319) configure backup of stats.phx.ovirt.org

[Evgheni Dereveanchin (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Evgheni Dereveanchin updated OVIRT-1319:

Epic Link: OVIRT-2194

> configure backup of stats.phx.ovirt.org
> ---
>
> Key: OVIRT-1319
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1319
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Evgheni Dereveanchin
>Assignee: infra
>Priority: Low
>  Labels: backup, phx
>
> The stats server is accumulating historical data, backups need to be set up 
> so that we don't risk losing it.



--
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/FZPXGGZGOTXP32ZFGOMB5SY3RXYJG3JU/

[JIRA] (OVIRT-2183) Automate creation of "poll" jobs

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-2183:

Resolution: Duplicate
Status: Done  (was: To Do)

Closing as duplicate of OVIRT-1876

> Automate creation of "poll" jobs
> 
>
> Key: OVIRT-2183
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2183
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Standard CI (Pipelines)
>Reporter: Barak Korren
>Assignee: infra
>
> As a developer I would like to be able to configure upstream source polling 
> jobs (In other works jobs that execute the "poll-upstream-sources" STDCI 
> stage) from the STDCI YAML file in my project so that I never have to deal 
> with JJB or the 'jenkins' repository.
> h3. Acceptance Criteria
> # To get "poll-upstream-sources" jobs working for a certain branch developers 
> should only configure some setting in the STDCI YAML file of that project. 



--
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/KOSGDK4BVQ4A45CA7PSYILC2NJZOZZLK/

[JIRA] (OVIRT-2034) Recreate the transactional CI mirrors with Pulp

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-2034:
-
Epic Link:   (was: OVIRT-403)

> Recreate the transactional CI mirrors with Pulp
> ---
>
> Key: OVIRT-2034
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2034
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: CI Mirrors
>Reporter: Barak Korren
>Assignee: infra
>
> Right now, the CI mirrors are created and maintained by a set of custom 
> scripts and jobs.
> It seems that [Pulp|https://pulpproject.org/] can do what our current system 
> does. The reason behind not using it when we first made the mirrors system 
> was out desire to provide a quick solution and avoid adding more services to 
> maintain. 
> There are however, quite a few reasons to want to switch to pulp:
> # Aside from RPMs it can also manage other interesting kinds of resources 
> like Containers, DEB packages and Python packages.
> # If it works well for us - we can maintain less code by dropping the 
> existing mirror management code
> # It has built-in distribution mechanisms that can be useful to scale it up. 
> # It seems it has support for assigning packages to multiple repos. This cab 
> be used as a tagging mechanism to implement OVIRT-2033



--
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/JB3R3GIG3AG3K6BMGWWGPYK5BWFOAV7P/

[JIRA] (OVIRT-2034) Recreate the transactional CI mirrors with Pulp

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-2034:
-
Epic Link: (was: OVIRT-403)

> Recreate the transactional CI mirrors with Pulp
> ---
>
> Key: OVIRT-2034
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2034
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: CI Mirrors
>Reporter: Barak Korren
>Assignee: infra
>
> Right now, the CI mirrors are created and maintained by a set of custom 
> scripts and jobs.
> It seems that [Pulp|https://pulpproject.org/] can do what our current system 
> does. The reason behind not using it when we first made the mirrors system 
> was out desire to provide a quick solution and avoid adding more services to 
> maintain. 
> There are however, quite a few reasons to want to switch to pulp:
> # Aside from RPMs it can also manage other interesting kinds of resources 
> like Containers, DEB packages and Python packages.
> # If it works well for us - we can maintain less code by dropping the 
> existing mirror management code
> # It has built-in distribution mechanisms that can be useful to scale it up. 
> # It seems it has support for assigning packages to multiple repos. This cab 
> be used as a tagging mechanism to implement OVIRT-2033



--
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/GUQTQ3M7APJIRAMXWJ7GCUMP27AN5AOA/

[JIRA] (OVIRT-2194) Backup oVirt servers and services

[eyal edri (oVirt JIRA)]

eyal edri created OVIRT-2194:


 Summary: Backup oVirt servers and services
 Key: OVIRT-2194
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2194
 Project: oVirt - virtualization made easy
  Issue Type: Epic
Reporter: eyal edri
Assignee: infra
Priority: High






--
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/AV7JQDL5PETH4APPGLRDUDBHBHITK7RJ/

[JIRA] (OVIRT-1319) configure backup of stats.phx.ovirt.org

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1319:
-
Epic Link:   (was: OVIRT-403)

> configure backup of stats.phx.ovirt.org
> ---
>
> Key: OVIRT-1319
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1319
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Evgheni Dereveanchin
>Assignee: infra
>Priority: Low
>
> The stats server is accumulating historical data, backups need to be set up 
> so that we don't risk losing it.



--
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/IMGBQ24TYNDU7F6KZEZ6LPOHO27L3JN6/

[JIRA] (OVIRT-1319) configure backup of stats.phx.ovirt.org

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1319:
-
Labels: backup phx  (was: )

> configure backup of stats.phx.ovirt.org
> ---
>
> Key: OVIRT-1319
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1319
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Evgheni Dereveanchin
>Assignee: infra
>Priority: Low
>  Labels: backup, phx
>
> The stats server is accumulating historical data, backups need to be set up 
> so that we don't risk losing it.



--
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/7GY4JIACNJDEUIWKHE2WJU7AQUHEM5M6/

[JIRA] (OVIRT-1319) configure backup of stats.phx.ovirt.org

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1319:
-
Epic Link: (was: OVIRT-403)

> configure backup of stats.phx.ovirt.org
> ---
>
> Key: OVIRT-1319
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1319
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Evgheni Dereveanchin
>Assignee: infra
>Priority: Low
>
> The stats server is accumulating historical data, backups need to be set up 
> so that we don't risk losing it.



--
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/2HT4GS3B3RLI6Y67DSCQA556Y3ZSQXDE/

[JIRA] (OVIRT-1333) Exclude game/desktop packages from mirrors

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1333:
-
Labels: Icebox first_time_task  (was: first_time_task)

> Exclude game/desktop packages from mirrors
> --
>
> Key: OVIRT-1333
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1333
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Repositories Mgmt
>Reporter: Barak Korren
>Assignee: infra
>  Labels: Icebox, first_time_task
>
> Our mirrors currently contain full copies of the CentOS and Fedora repos, 
> including many large game and desktop productivity packages. 
> We should probably clean these packages from the repos to save space and 
> bandwidth.



--
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/WTKD5KQ2256L5XJLV7ES2ZI5SLUMI6OX/

[JIRA] (OVIRT-1333) Exclude game/desktop packages from mirrors

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1333:
-
Epic Link:   (was: OVIRT-403)

> Exclude game/desktop packages from mirrors
> --
>
> Key: OVIRT-1333
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1333
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Repositories Mgmt
>Reporter: Barak Korren
>Assignee: infra
>  Labels: first_time_task
>
> Our mirrors currently contain full copies of the CentOS and Fedora repos, 
> including many large game and desktop productivity packages. 
> We should probably clean these packages from the repos to save space and 
> bandwidth.



--
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/4R5JSTBMAMG4ZNQIDPLW3U36EQ7KEZGO/

[JIRA] (OVIRT-1333) Exclude game/desktop packages from mirrors

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1333:
-
Epic Link: (was: OVIRT-403)

> Exclude game/desktop packages from mirrors
> --
>
> Key: OVIRT-1333
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1333
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Repositories Mgmt
>Reporter: Barak Korren
>Assignee: infra
>  Labels: first_time_task
>
> Our mirrors currently contain full copies of the CentOS and Fedora repos, 
> including many large game and desktop productivity packages. 
> We should probably clean these packages from the repos to save space and 
> bandwidth.



--
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/ZSCCB4HUXNZVXUPHBNK243MCJGOUMQTK/

[JIRA] (OVIRT-1877) Update docs to indicated adding 'jenkins:' prefix to build URLs

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1877:

Epic Link:   (was: OVIRT-400)

> Update docs to indicated adding 'jenkins:' prefix to build URLs
> ---
>
> Key: OVIRT-1877
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Barak Korren
>Assignee: infra
>
> Our infra includes multipile places where users can input text that is used 
> as configuration for repoman. Users are typically expected to place URLs of 
> build jobs there to make repoman acquire built artifacts (For e.g. testing).
> So far documentation specified that the plain URL to the build job can be 
> used. This turns out to only be true for builds made on jenkins.ovirt.org. 
> For URLs pointing at other jenkins servers, the '{{jenkins:}}' prefix needs 
> to be added.
> Documentation should be updated to teach users to add the '{{jenkins:}}' 
> prefix.



--
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/GVZTVQUX56LV4MNAHEXFS46ZQEC2NK5B/

[JIRA] (OVIRT-1877) Update docs to indicated adding 'jenkins:' prefix to build URLs

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1877:

Epic Link: (was: OVIRT-400)

> Update docs to indicated adding 'jenkins:' prefix to build URLs
> ---
>
> Key: OVIRT-1877
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1877
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Barak Korren
>Assignee: infra
>
> Our infra includes multipile places where users can input text that is used 
> as configuration for repoman. Users are typically expected to place URLs of 
> build jobs there to make repoman acquire built artifacts (For e.g. testing).
> So far documentation specified that the plain URL to the build job can be 
> used. This turns out to only be true for builds made on jenkins.ovirt.org. 
> For URLs pointing at other jenkins servers, the '{{jenkins:}}' prefix needs 
> to be added.
> Documentation should be updated to teach users to add the '{{jenkins:}}' 
> prefix.



--
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/X3I54PH6343KVK7S52375MZPYAXSXCWH/

[JIRA] (OVIRT-1878) GitHub support for pusher.py

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1878:

Epic Link: (was: OVIRT-400)

> GitHub support for pusher.py
> 
>
> Key: OVIRT-1878
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1878
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: pusher.py
>Reporter: Barak Korren
>Assignee: infra
>  Labels: first_time_task, github
>
> '{{pusher.py}}' currently only supports gerrit, what this means in practice 
> is that automated polling for upstream source changes is only available for 
> repos that are hosted in Gerrit.
> We need to support this in GitHub as well.



--
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/43PT43BMJO5E55XOWESFJZPQ63QA7HXX/

[JIRA] (OVIRT-1878) GitHub support for pusher.py

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1878:

Epic Link:   (was: OVIRT-400)

> GitHub support for pusher.py
> 
>
> Key: OVIRT-1878
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1878
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: pusher.py
>Reporter: Barak Korren
>Assignee: infra
>  Labels: first_time_task, github
>
> '{{pusher.py}}' currently only supports gerrit, what this means in practice 
> is that automated polling for upstream source changes is only available for 
> repos that are hosted in Gerrit.
> We need to support this in GitHub as well.



--
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/EEI53DZ4HUNZLWY2TNOUQ3V7G2MUCSXR/

[JIRA] (OVIRT-1885) Remove slave/resource management from Jenkins

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1885:

Epic Link:   (was: OVIRT-400)

> Remove slave/resource management from Jenkins
> -
>
> Key: OVIRT-1885
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1885
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins Master, Jenkins Slaves
>Reporter: Barak Korren
>Assignee: infra
>  Labels: scale
>
> The way out infra is configure right now, resource allocation and management 
> is done by Jenkins itself. This means that all resources need to 
> pre-allocated to Jenkins in the form of slaves.
> If we want to have separate Jenkins masters, our current configuration will 
> force us to hard-split the resources between different Jenkins masters.
> If we want to share our pool of resources between multiple masters, it means 
> that resource allocation needs to move out of Jenkins to external tools.
> Potential tools for different types of resources are:
> * Beaker for managing physical hosts
> * oVirt + a Jenkins could provider plugin for managing VMs
> * OpenShift for managing containers (As a replacement for chroots).



--
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/FMUSGMAG3MQTOA3WZJQYYYS7YEYKQW5B/

[JIRA] (OVIRT-1885) Remove slave/resource management from Jenkins

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren reassigned OVIRT-1885:
---

Assignee: (was: infra)

> Remove slave/resource management from Jenkins
> -
>
> Key: OVIRT-1885
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1885
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins Master, Jenkins Slaves
>Reporter: Barak Korren
>  Labels: scale
>
> The way out infra is configure right now, resource allocation and management 
> is done by Jenkins itself. This means that all resources need to 
> pre-allocated to Jenkins in the form of slaves.
> If we want to have separate Jenkins masters, our current configuration will 
> force us to hard-split the resources between different Jenkins masters.
> If we want to share our pool of resources between multiple masters, it means 
> that resource allocation needs to move out of Jenkins to external tools.
> Potential tools for different types of resources are:
> * Beaker for managing physical hosts
> * oVirt + a Jenkins could provider plugin for managing VMs
> * OpenShift for managing containers (As a replacement for chroots).



--
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/K7HORDX5TAXDIYH7M2WOW6WLQEVBTQ7K/

[JIRA] (OVIRT-1885) Remove slave/resource management from Jenkins

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1885:

Epic Link: (was: OVIRT-400)

> Remove slave/resource management from Jenkins
> -
>
> Key: OVIRT-1885
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1885
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Jenkins Master, Jenkins Slaves
>Reporter: Barak Korren
>Assignee: infra
>  Labels: scale
>
> The way out infra is configure right now, resource allocation and management 
> is done by Jenkins itself. This means that all resources need to 
> pre-allocated to Jenkins in the form of slaves.
> If we want to have separate Jenkins masters, our current configuration will 
> force us to hard-split the resources between different Jenkins masters.
> If we want to share our pool of resources between multiple masters, it means 
> that resource allocation needs to move out of Jenkins to external tools.
> Potential tools for different types of resources are:
> * Beaker for managing physical hosts
> * oVirt + a Jenkins could provider plugin for managing VMs
> * OpenShift for managing containers (As a replacement for chroots).



--
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/SRRD54M2YUAQ56TFMDZNEX2K7G4W2575/

[JIRA] (OVIRT-1615) Replace Artifactory with Nexus

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1615:
-
Epic Link:   (was: OVIRT-403)

> Replace Artifactory with Nexus
> --
>
> Key: OVIRT-1615
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1615
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: General
>Reporter: Barak Korren
>Assignee: infra
>Priority: Lowest
>  Labels: Icebox
>
> Nexus is the main competitor to Artifactory. It has similar features.  
> Lokking at documentation available about it, it looks like the open source 
> version of it supports a much bigger feature set the Artifactory without 
> requiring an upgrade to a payed version:
> https://help.sonatype.com/display/NXRM3/Repository+Manager+Feature+Matrix
> Of interest to us are the PyPi (Python) support, the NPM (Javascript) and the 
> Docker support.
> It seems that Nexus is available as a container, so we may try deploying it 
> on OpenShift.
> I think we need to plan and execute a migration to Nexus.
> This ticket should server as a tracking ticket for the entire work. We will 
> create blocker tickets to track needed steps. 



--
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/BI4HXDU4DCUTQWOXMYBSCPMVHNYGTPWP/

[JIRA] (OVIRT-1615) Replace Artifactory with Nexus

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1615:
-
Epic Link: (was: OVIRT-403)

> Replace Artifactory with Nexus
> --
>
> Key: OVIRT-1615
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1615
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: General
>Reporter: Barak Korren
>Assignee: infra
>Priority: Lowest
>  Labels: Icebox
>
> Nexus is the main competitor to Artifactory. It has similar features.  
> Lokking at documentation available about it, it looks like the open source 
> version of it supports a much bigger feature set the Artifactory without 
> requiring an upgrade to a payed version:
> https://help.sonatype.com/display/NXRM3/Repository+Manager+Feature+Matrix
> Of interest to us are the PyPi (Python) support, the NPM (Javascript) and the 
> Docker support.
> It seems that Nexus is available as a container, so we may try deploying it 
> on OpenShift.
> I think we need to plan and execute a migration to Nexus.
> This ticket should server as a tracking ticket for the entire work. We will 
> create blocker tickets to track needed steps. 



--
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/O3SRCFMXMJBA554PFTBDOO4GKDG3EWGT/

[JIRA] (OVIRT-1615) Replace Artifactory with Nexus

[eyal edri (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri updated OVIRT-1615:
-
Labels: Icebox  (was: )

> Replace Artifactory with Nexus
> --
>
> Key: OVIRT-1615
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1615
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: General
>Reporter: Barak Korren
>Assignee: infra
>Priority: Lowest
>  Labels: Icebox
>
> Nexus is the main competitor to Artifactory. It has similar features.  
> Lokking at documentation available about it, it looks like the open source 
> version of it supports a much bigger feature set the Artifactory without 
> requiring an upgrade to a payed version:
> https://help.sonatype.com/display/NXRM3/Repository+Manager+Feature+Matrix
> Of interest to us are the PyPi (Python) support, the NPM (Javascript) and the 
> Docker support.
> It seems that Nexus is available as a container, so we may try deploying it 
> on OpenShift.
> I think we need to plan and execute a migration to Nexus.
> This ticket should server as a tracking ticket for the entire work. We will 
> create blocker tickets to track needed steps. 



--
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/ASGZYHAERJ2IBSWXB7LKGYIRXZB3QDG3/

[JIRA] (OVIRT-1920) Modify ci_env_client.py to be case and signs insensitive

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1920:

Epic Link:   (was: OVIRT-400)

> Modify ci_env_client.py to be case and signs insensitive
> 
>
> Key: OVIRT-1920
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1920
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: mock_runner
>Reporter: Daniel Belenky
>Assignee: infra
>
> In OVIRT-1892 we make stdci config be case and signs insensitive. It means 
> that when we will write a runner (or modify mock_runner) to use the new 
> config, ci_env_client will have to deal with a normalized structure (without 
> cases nor signs as dots and dashes).



--
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/R2PTAQ6UX2LIDYTHARMRHRI5SSKNBIEK/

[JIRA] (OVIRT-1920) Modify ci_env_client.py to be case and signs insensitive

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1920:

Component/s: (was: STDCI DSL)
 (was: Standard CI (Pipelines))
 mock_runner

> Modify ci_env_client.py to be case and signs insensitive
> 
>
> Key: OVIRT-1920
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1920
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: mock_runner
>Reporter: Daniel Belenky
>Assignee: infra
>
> In OVIRT-1892 we make stdci config be case and signs insensitive. It means 
> that when we will write a runner (or modify mock_runner) to use the new 
> config, ci_env_client will have to deal with a normalized structure (without 
> cases nor signs as dots and dashes).



--
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/PNBRJZAHOTOBZC5Z5IZQXRLZZA3SW24C/

[JIRA] (OVIRT-1920) Modify ci_env_client.py to be case and signs insensitive

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1920:

Epic Link: (was: OVIRT-400)

> Modify ci_env_client.py to be case and signs insensitive
> 
>
> Key: OVIRT-1920
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1920
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: mock_runner
>Reporter: Daniel Belenky
>Assignee: infra
>
> In OVIRT-1892 we make stdci config be case and signs insensitive. It means 
> that when we will write a runner (or modify mock_runner) to use the new 
> config, ci_env_client will have to deal with a normalized structure (without 
> cases nor signs as dots and dashes).



--
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/EQTOOHDUXG4U6SYCLNVXOXIL5QGSPM4B/

[JIRA] (OVIRT-1945) Allow to keep running containers in docker_cleanup

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1945:

Epic Link: (was: OVIRT-400)

> Allow to keep running containers in docker_cleanup
> --
>
> Key: OVIRT-1945
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1945
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt CI, Standard CI (Freestyle), Standard CI 
> (Pipelines)
>Reporter: Daniel Belenky
>Assignee: infra
>  Labels: standard-ci
>
> docker_cleanup.py stops all running containers before it removes the images.
> We should make it optional as well as allow whitelisting containers.



--
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/BFQEYYEQ77IBBXHUYOWJ6PHTPPDMMXHN/

[JIRA] (OVIRT-1945) Allow to keep running containers in docker_cleanup

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1945:

Epic Link:   (was: OVIRT-400)

> Allow to keep running containers in docker_cleanup
> --
>
> Key: OVIRT-1945
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1945
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: oVirt CI, Standard CI (Freestyle), Standard CI 
> (Pipelines)
>Reporter: Daniel Belenky
>Assignee: infra
>  Labels: standard-ci
>
> docker_cleanup.py stops all running containers before it removes the images.
> We should make it optional as well as allow whitelisting containers.



--
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/KXYGXOIAYJVODJZWXLAFDZT3HAGR66BA/

[JIRA] (OVIRT-1953) Add PPC mirrors

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1953:

Resolution: Duplicate
Status: Done  (was: To Do)

Closing as duplicate of OVIRT-2041

> Add PPC mirrors
> ---
>
> Key: OVIRT-1953
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1953
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: CI Mirrors
>Reporter: Daniel Belenky
>Assignee: infra
>




--
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/X4JHAWWPWGKNX2AN3MG2BMEWDUQESACL/

[JIRA] (OVIRT-1953) Add PPC mirrors

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1953:

Epic Link:   (was: OVIRT-400)

> Add PPC mirrors
> ---
>
> Key: OVIRT-1953
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1953
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: CI Mirrors
>Reporter: Daniel Belenky
>Assignee: infra
>




--
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/B2FTMFHU3R3LZZM4B55VKJWPJFUICUEW/

[JIRA] (OVIRT-1953) Add PPC mirrors

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1953:

Epic Link: (was: OVIRT-400)

> Add PPC mirrors
> ---
>
> Key: OVIRT-1953
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1953
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: CI Mirrors
>Reporter: Daniel Belenky
>Assignee: infra
>




--
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/ZHNUUKQIBMD2NACTKQJ3EFR7GZ4MXUC2/

[JIRA] (OVIRT-1958) Allow custom checkout dir

[Barak Korren (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37038#comment-37038
 ] 

Barak Korren commented on OVIRT-1958:
-

[~dbele...@redhat.com] I think we fixed this already no? there is no patch 
attached...

> Allow custom checkout dir
> -
>
> Key: OVIRT-1958
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1958
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: infra
>
> Currently, we assume that the checkout dir has the same name as the project. 
> This should be configurable by environment variable passed from JJB.



--
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/ZIVVZAFOREF5DLSCQYR7GZCCSMHBVFOP/

[JIRA] (OVIRT-1958) Allow custom checkout dir

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1958:

Epic Link:   (was: OVIRT-400)

> Allow custom checkout dir
> -
>
> Key: OVIRT-1958
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1958
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: infra
>
> Currently, we assume that the checkout dir has the same name as the project. 
> This should be configurable by environment variable passed from JJB.



--
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/A3JYCZYOOOKBLGTWYTGGD75J7JN7ALR4/

[JIRA] (OVIRT-1959) Make usrc.py support Git tags

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1959:

Epic Link: OVIRT-1124  (was: OVIRT-400)

> Make usrc.py support Git tags
> -
>
> Key: OVIRT-1959
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1959
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: usrc.py
>Reporter: Barak Korren
>Assignee: infra
>
> There are multiple features that could be useful to add to {{usrc.py}} that 
> has to do with Git tags:
> # *Snap to tag* - when running {{update}} take the latest tagged commit from 
> the branch instead of the latest commit. This could further be enhanced to 
> decide what to do when there is no tagged commit that is newer then what we 
> already have - we can either decide not to update or update to the latest 
> (untagged) commit.
> # *Copy tag* - when running with {{--commit}} and the upstream commit we're 
> updating into is tagged, store some information somewhere so that if the 
> commit is merged, the CI system could tag it automatically and push that tag. 
> It should be possible to customise the tag we add to allow it to be different 
> but derived from the upstream tag. One possible place to store the needed 
> information is to use a header in the commit message like we do for 
> auto-merge.



--
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/JC6PYSG7TUKG7QPQTFWL5GLVAXMCI5F6/

[JIRA] (OVIRT-1958) Allow custom checkout dir

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1958:

Epic Link: (was: OVIRT-400)

> Allow custom checkout dir
> -
>
> Key: OVIRT-1958
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1958
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Daniel Belenky
>Assignee: infra
>
> Currently, we assume that the checkout dir has the same name as the project. 
> This should be configurable by environment variable passed from JJB.



--
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/OFPX2RHOA3WF5UPPI7ZHGHOXYFEO3LWK/

[JIRA] (OVIRT-1959) Make usrc.py support Git tags

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1959:

Epic Link: OVIRT-1124  (was: OVIRT-400)

> Make usrc.py support Git tags
> -
>
> Key: OVIRT-1959
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1959
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: usrc.py
>Reporter: Barak Korren
>Assignee: infra
>
> There are multiple features that could be useful to add to {{usrc.py}} that 
> has to do with Git tags:
> # *Snap to tag* - when running {{update}} take the latest tagged commit from 
> the branch instead of the latest commit. This could further be enhanced to 
> decide what to do when there is no tagged commit that is newer then what we 
> already have - we can either decide not to update or update to the latest 
> (untagged) commit.
> # *Copy tag* - when running with {{--commit}} and the upstream commit we're 
> updating into is tagged, store some information somewhere so that if the 
> commit is merged, the CI system could tag it automatically and push that tag. 
> It should be possible to customise the tag we add to allow it to be different 
> but derived from the upstream tag. One possible place to store the needed 
> information is to use a header in the commit message like we do for 
> auto-merge.



--
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/BP34Z2Z2ER7ONEGUOXVBBRBFOV6KQUUL/

[JIRA] (OVIRT-1960) Make pusehr.py able to push Git tags

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1960:

Epic Link: (was: OVIRT-400)

> Make pusehr.py able to push Git tags
> 
>
> Key: OVIRT-1960
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1960
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: pusher.py
>Reporter: Barak Korren
>Assignee: infra
>
> {{pusher.py}} knows how to push patches into remote SCMs. WE should also add 
> functionality for pushing tags. More specifically:
> # It should be possible to request that and arbitrary tag for HEAD be created 
> and pushed. This should make it possible to implement OVIRT-1717
> # It should be possible to create and push a tag with information that is 
> gathered and created by {{usrc.py}}. This is a counterpart to OVIRT-1959



--
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/4HWOWDQDCOAMQ6Q5RN4POWGAJYQX6FXG/

[JIRA] (OVIRT-1960) Make pusehr.py able to push Git tags

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1960:

Epic Link:   (was: OVIRT-400)

> Make pusehr.py able to push Git tags
> 
>
> Key: OVIRT-1960
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1960
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: pusher.py
>Reporter: Barak Korren
>Assignee: infra
>
> {{pusher.py}} knows how to push patches into remote SCMs. WE should also add 
> functionality for pushing tags. More specifically:
> # It should be possible to request that and arbitrary tag for HEAD be created 
> and pushed. This should make it possible to implement OVIRT-1717
> # It should be possible to create and push a tag with information that is 
> gathered and created by {{usrc.py}}. This is a counterpart to OVIRT-1959



--
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/ASPWDN6MUHQWNSOWKAMMYYYFGVZ5VQUY/

[JIRA] (OVIRT-1963) Nicer UI for OST manual job

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1963:

Epic Link: OVIRT-2185  (was: OVIRT-400)

> Nicer UI for OST manual job 
> 
>
> Key: OVIRT-1963
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1963
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: OST Manual job
>Reporter: Barak Korren
>Assignee: infra
>  Labels: first_time_task
>
> Make the following details shown in the builds list of the OST manual job so 
> that finding a particular build in the builds list is easier:
> # The person who triggered the build
> # The suit that was run
> # The amount of URLs passed into extra-sources, and if possible - the name of 
> the project whose modified packages were included.



--
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/4A5AOKSSVCH3BPBEZKIBAJE2B6FTSWQS/

[JIRA] (OVIRT-1963) Nicer UI for OST manual job

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1963:

Epic Link: OVIRT-2185  (was: OVIRT-400)

> Nicer UI for OST manual job 
> 
>
> Key: OVIRT-1963
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1963
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: OST Manual job
>Reporter: Barak Korren
>Assignee: infra
>  Labels: first_time_task
>
> Make the following details shown in the builds list of the OST manual job so 
> that finding a particular build in the builds list is easier:
> # The person who triggered the build
> # The suit that was run
> # The amount of URLs passed into extra-sources, and if possible - the name of 
> the project whose modified packages were included.



--
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/HF6P7EMUNXHHENO44NG5JFQLX44VQT4I/

[JIRA] (OVIRT-1965) Add failure details to CQ messages

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1965:

Epic Link: OVIRT-2185  (was: OVIRT-400)

> Add failure details to CQ messages
> --
>
> Key: OVIRT-1965
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1965
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Change Queue
>Reporter: Barak Korren
>Assignee: infra
>
> In order to streamline the process for debugging CQ issues, we should have 
> more failure details added to the messages it sends. Those details should 
> include:
> # The names of the OST suits that failed
> # The OST tests that failed
> # If it was a build failure rather then an OST failure
> # If it was possible to detect - the particular change(s) that caused failure.
>  #if its possible to tell - if its an infra issue or a code regression
> To implement this we would need at the very least a richer interface for 
> passing information between the CQ tester and the and manager jobs - possibly 
> some kind of a structured data file passed around. We may also need a richer 
> interface to OST itself (to tell which test failed) and perhaps even to the 
> build jobs (to tell why the build failed).  



--
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/VUMXNJGQBYPJBCC56ZPQADK3RDUE34M4/

[JIRA] (OVIRT-1965) Add failure details to CQ messages

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1965:

Epic Link: OVIRT-2185  (was: OVIRT-400)

> Add failure details to CQ messages
> --
>
> Key: OVIRT-1965
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1965
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Change Queue
>Reporter: Barak Korren
>Assignee: infra
>
> In order to streamline the process for debugging CQ issues, we should have 
> more failure details added to the messages it sends. Those details should 
> include:
> # The names of the OST suits that failed
> # The OST tests that failed
> # If it was a build failure rather then an OST failure
> # If it was possible to detect - the particular change(s) that caused failure.
>  #if its possible to tell - if its an infra issue or a code regression
> To implement this we would need at the very least a richer interface for 
> passing information between the CQ tester and the and manager jobs - possibly 
> some kind of a structured data file passed around. We may also need a richer 
> interface to OST itself (to tell which test failed) and perhaps even to the 
> build jobs (to tell why the build failed).  



--
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/LW44KV7FLE7HDQOWDSDQ4ZY4CTFZ6XS2/

[JIRA] (OVIRT-1973) vdsm_master_check-patch-fc27 fail due to yum repo issues

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1973:

Issue Type: Outage  (was: By-EMAIL)

> vdsm_master_check-patch-fc27 fail due to yum repo issues
> 
>
> Key: OVIRT-1973
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1973
> Project: oVirt - virtualization made easy
>  Issue Type: Outage
>  Components: CI client projects
>Reporter: danken
>Assignee: infra
>
> Once in a while, jobs are failing due to
> [MIRROR] kmod-kvdo-6.1.1.24-1.fc27.x86_64.rpm: Downloading successful,
> but checksum doesn't match. Calculated:
> 54996f8e7877b533bf43825853cd3c7cfd0f7df5cb6a1876e50c9ade7829dd73(sha256)
>  Expected: 
> 7a8294588764bd2c14adaa7d24218cce344930c1ce62a24b17208d1cd629c461(sha256)
> for example
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/2830/consoleText



--
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/4HSR5X2V7IVGZHYDKBIYC4RMD35NF3CU/

[JIRA] (OVIRT-1973) vdsm_master_check-patch-fc27 fail due to yum repo issues

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1973:

Epic Link:   (was: OVIRT-400)

> vdsm_master_check-patch-fc27 fail due to yum repo issues
> 
>
> Key: OVIRT-1973
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1973
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>  Components: CI client projects
>Reporter: danken
>Assignee: infra
>
> Once in a while, jobs are failing due to
> [MIRROR] kmod-kvdo-6.1.1.24-1.fc27.x86_64.rpm: Downloading successful,
> but checksum doesn't match. Calculated:
> 54996f8e7877b533bf43825853cd3c7cfd0f7df5cb6a1876e50c9ade7829dd73(sha256)
>  Expected: 
> 7a8294588764bd2c14adaa7d24218cce344930c1ce62a24b17208d1cd629c461(sha256)
> for example
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/2830/consoleText



--
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/QZQAS6SMQXUDV6ABHWUJVCVKCOFBDW3E/

[JIRA] (OVIRT-1983) Switch to using JJB >= 2.0.6

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1983:

Epic Link:   (was: OVIRT-400)

> Switch to using JJB >= 2.0.6
> 
>
> Key: OVIRT-1983
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1983
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: JJB
>Reporter: Barak Korren
>Assignee: infra
>
> Version 2.0.6 is the latest released version of JJB at the time of this 
> writing. We've been using a very old development version of JJB (1.4.1.dev50) 
> for a long time and its about time we upgraded. Other then that the post 
> 2.0.0 has one major feature which is Jinja2 support which may be very useful 
> for us.
> In order to upgrade, we probably need to implement OVIRT-1466 first.



--
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/GTKW5H3ENP44IAOZE2FOCDFZRIN6SPYD/

[JIRA] (OVIRT-1973) vdsm_master_check-patch-fc27 fail due to yum repo issues

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1973:

Epic Link: (was: OVIRT-400)

> vdsm_master_check-patch-fc27 fail due to yum repo issues
> 
>
> Key: OVIRT-1973
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1973
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>  Components: CI client projects
>Reporter: danken
>Assignee: infra
>
> Once in a while, jobs are failing due to
> [MIRROR] kmod-kvdo-6.1.1.24-1.fc27.x86_64.rpm: Downloading successful,
> but checksum doesn't match. Calculated:
> 54996f8e7877b533bf43825853cd3c7cfd0f7df5cb6a1876e50c9ade7829dd73(sha256)
>  Expected: 
> 7a8294588764bd2c14adaa7d24218cce344930c1ce62a24b17208d1cd629c461(sha256)
> for example
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc27-x86_64/2830/consoleText



--
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/M7MZPTBUYKSDIQKF5GKUM5SA56MFTQ35/

[JIRA] (OVIRT-1983) Switch to using JJB >= 2.0.6

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1983:

Epic Link: (was: OVIRT-400)

> Switch to using JJB >= 2.0.6
> 
>
> Key: OVIRT-1983
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1983
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: JJB
>Reporter: Barak Korren
>Assignee: infra
>
> Version 2.0.6 is the latest released version of JJB at the time of this 
> writing. We've been using a very old development version of JJB (1.4.1.dev50) 
> for a long time and its about time we upgraded. Other then that the post 
> 2.0.0 has one major feature which is Jinja2 support which may be very useful 
> for us.
> In order to upgrade, we probably need to implement OVIRT-1466 first.



--
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/DPCBAVTMNMSGQYUV7S24RPHEGMO77RN2/

[JIRA] (OVIRT-1984) Create "out-of-band" slave cleanup and setup jobs

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1984:

Epic Link: OVIRT-2178  (was: OVIRT-400)

> Create "out-of-band" slave cleanup and setup jobs
> -
>
> Key: OVIRT-1984
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1984
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Jenkins Slaves
>Reporter: Barak Korren
>Assignee: infra
>
> Right now, we run slave cleaup and setup steps as part or every single job we 
> run. This has several shortcomings:
> # It takes a long time from the point a user submitted a patch to the point 
> his actual test or build code runs
> # If slave setup or cleanup steps fail - they fail the whole job for the user
> # If slave setup or cleanup steps fail - they can keep failing for many jobs 
> until the CI team intervenes manually
> # There is a "chicken and an egg" issue where some parts of the CI code have 
> to run before the slave was properly cleaned up and configured.  This makes 
> if harder to add new slaves for the system.
> Here is a suggested scheme to fix all this:
> # Label all slaves that should be cleaned up automatically as 'cleanable'. 
> This is mostly to prevent the jobs described here from operating on the 
> master node.
> # Have a "cleanup scheduler" job that finds all slaves labelled as 
> "cleanable" but not as "dirty" or "clean", labels them as "dirty" and runs a 
> cleanup job on them.
> # Have a "cleanup" job that is triggered on particular slaves by the "cleanup 
> scheduler" job, runs cleaup and setup steps on them and then labels them as 
> "clean" and removes the "dirty" label.
> # Have all other CI jobs only use slaves with the "clean" label.
> Notes:
> # The "dirty" label is there to make the "cleanup scheduler" job not trigger 
> twice on the same slave before the"cleanup" job started cleaning it up.
> # Since all slaves used by the real jobs will always be clean - there will no 
> longer be a need to run cleanup steps in the real jobs, thus saving time.
> # If cleanup steps fail - the cleanup job will fail and the slave will not be 
> marked as "clean" so real jobs will never try to use it.
> # To solve the "chicken and egg" issue, the cleanup job probably must be a 
> FreeStyle jobs and all the cleanup and setup code must be embedded into it by 
> JJB. This will probably require a newer version of JJB then what we have so 
> setting OVIRT-1983 as a blocker.
> # There is an issue of how to make CI for this - if cleanup and setup steps 
> are removed from the normal STDCI jobs, they they will not be checked by the 
> "check-patch" job of the "jenkins repo". Here is a suggested scheme to solve 
> this:
> ## Have a way to "loan" slaves from the production jenkins to other Jenkins 
> instances - this could be done by having a job that starts up the Jenkins 
> JNLP client and tells it to connect to another Jenkins master.
> ## As part of the "check-patch" job for the 'jenkins' repo - start a Jenkins 
> master in a container - attach some production slaves to it and have it run 
> cleanup and setup steps on them  



--
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/FCTDRGYEV4C3IIKMTTRHCBA2WBTYR2OV/

[JIRA] (OVIRT-1984) Create "out-of-band" slave cleanup and setup jobs

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1984:

Epic Link: OVIRT-2178  (was: OVIRT-400)

> Create "out-of-band" slave cleanup and setup jobs
> -
>
> Key: OVIRT-1984
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1984
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Jenkins Slaves
>Reporter: Barak Korren
>Assignee: infra
>
> Right now, we run slave cleaup and setup steps as part or every single job we 
> run. This has several shortcomings:
> # It takes a long time from the point a user submitted a patch to the point 
> his actual test or build code runs
> # If slave setup or cleanup steps fail - they fail the whole job for the user
> # If slave setup or cleanup steps fail - they can keep failing for many jobs 
> until the CI team intervenes manually
> # There is a "chicken and an egg" issue where some parts of the CI code have 
> to run before the slave was properly cleaned up and configured.  This makes 
> if harder to add new slaves for the system.
> Here is a suggested scheme to fix all this:
> # Label all slaves that should be cleaned up automatically as 'cleanable'. 
> This is mostly to prevent the jobs described here from operating on the 
> master node.
> # Have a "cleanup scheduler" job that finds all slaves labelled as 
> "cleanable" but not as "dirty" or "clean", labels them as "dirty" and runs a 
> cleanup job on them.
> # Have a "cleanup" job that is triggered on particular slaves by the "cleanup 
> scheduler" job, runs cleaup and setup steps on them and then labels them as 
> "clean" and removes the "dirty" label.
> # Have all other CI jobs only use slaves with the "clean" label.
> Notes:
> # The "dirty" label is there to make the "cleanup scheduler" job not trigger 
> twice on the same slave before the"cleanup" job started cleaning it up.
> # Since all slaves used by the real jobs will always be clean - there will no 
> longer be a need to run cleanup steps in the real jobs, thus saving time.
> # If cleanup steps fail - the cleanup job will fail and the slave will not be 
> marked as "clean" so real jobs will never try to use it.
> # To solve the "chicken and egg" issue, the cleanup job probably must be a 
> FreeStyle jobs and all the cleanup and setup code must be embedded into it by 
> JJB. This will probably require a newer version of JJB then what we have so 
> setting OVIRT-1983 as a blocker.
> # There is an issue of how to make CI for this - if cleanup and setup steps 
> are removed from the normal STDCI jobs, they they will not be checked by the 
> "check-patch" job of the "jenkins repo". Here is a suggested scheme to solve 
> this:
> ## Have a way to "loan" slaves from the production jenkins to other Jenkins 
> instances - this could be done by having a job that starts up the Jenkins 
> JNLP client and tells it to connect to another Jenkins master.
> ## As part of the "check-patch" job for the 'jenkins' repo - start a Jenkins 
> master in a container - attach some production slaves to it and have it run 
> cleanup and setup steps on them  



--
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/Y3OR4S2H3CKQT24SAWDOKCYJEP43S2DN/

[JIRA] (OVIRT-1988) Add default behavior in secret_resolvers.py

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1988:

Labels: first_time_task  (was: )

> Add default behavior in secret_resolvers.py
> ---
>
> Key: OVIRT-1988
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1988
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: mock_runner
>Reporter: Daniel Belenky
>Assignee: infra
>  Labels: first_time_task
>
> Currently, when users try to run CI locally (currently with mock_runner),
> if their project has a secret dependency they have to either write a local
> secrets file, or to temporary modify their environment.yaml.
> The file format should have support for default behavior in case a secret
> was not found. Maybe something similar to:
> {code:java}
> ---
> - name: MY_SECRET
>   valueFrom:
> secretKeyRef:
>   name: secret_name
>   key: key_from_secret
>   default:
> from-env: ENV_VAR_NAME
> # OR
> value: default-value
> {code}



--
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/VTO6PWZMAMKHYD3S2R7OFWYKVV3Y/

[JIRA] (OVIRT-1988) Add default behavior in secret_resolvers.py

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1988:

Epic Link:   (was: OVIRT-400)

> Add default behavior in secret_resolvers.py
> ---
>
> Key: OVIRT-1988
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1988
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: mock_runner
>Reporter: Daniel Belenky
>Assignee: infra
>
> Currently, when users try to run CI locally (currently with mock_runner),
> if their project has a secret dependency they have to either write a local
> secrets file, or to temporary modify their environment.yaml.
> The file format should have support for default behavior in case a secret
> was not found. Maybe something similar to:
> {code:java}
> ---
> - name: MY_SECRET
>   valueFrom:
> secretKeyRef:
>   name: secret_name
>   key: key_from_secret
>   default:
> from-env: ENV_VAR_NAME
> # OR
> value: default-value
> {code}



--
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/GXZPNDL5VW5SSDVDHKVU23H3LXBINGXK/

[JIRA] (OVIRT-1991) jenkins triggers a build on a deleted branch

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1991:

Epic Link:   (was: OVIRT-400)

> jenkins triggers a build on a deleted branch
> 
>
> Key: OVIRT-1991
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1991
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Standard CI (Pipelines)
>Reporter: Roy Golan
>Assignee: infra
>Priority: Low
>
> I did some pruning, and removed old, unused branches, from
> https://github.com/oVirt/ovirt-openshift-extensions. Now I suddenly see my
> jenkins build is failing, because it triggered a build on the deleted
> branch.



--
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/PBOGTMOUVKTAAYQ4SRQBMWVUJKPYWK4D/

[JIRA] (OVIRT-1988) Add default behavior in secret_resolvers.py

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1988:

Epic Link: (was: OVIRT-400)

> Add default behavior in secret_resolvers.py
> ---
>
> Key: OVIRT-1988
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1988
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: mock_runner
>Reporter: Daniel Belenky
>Assignee: infra
>
> Currently, when users try to run CI locally (currently with mock_runner),
> if their project has a secret dependency they have to either write a local
> secrets file, or to temporary modify their environment.yaml.
> The file format should have support for default behavior in case a secret
> was not found. Maybe something similar to:
> {code:java}
> ---
> - name: MY_SECRET
>   valueFrom:
> secretKeyRef:
>   name: secret_name
>   key: key_from_secret
>   default:
> from-env: ENV_VAR_NAME
> # OR
> value: default-value
> {code}



--
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/Q6FNAQZ2ZIBDXBWSYJJVDYEL2MSC6DEI/

[JIRA] (OVIRT-1991) jenkins triggers a build on a deleted branch

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1991:

Epic Link: (was: OVIRT-400)

> jenkins triggers a build on a deleted branch
> 
>
> Key: OVIRT-1991
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1991
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Standard CI (Pipelines)
>Reporter: Roy Golan
>Assignee: infra
>Priority: Low
>
> I did some pruning, and removed old, unused branches, from
> https://github.com/oVirt/ovirt-openshift-extensions. Now I suddenly see my
> jenkins build is failing, because it triggered a build on the deleted
> branch.



--
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/447ORSURIPL5IFNLQF73RYHJMGJ33RDX/

[JIRA] (OVIRT-1996) Remove the 4.1 nightly publisher job

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1996:

Epic Link: OVIRT-2044  (was: OVIRT-400)

> Remove the 4.1 nightly publisher job
> 
>
> Key: OVIRT-1996
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1996
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Publisher jobs
>Reporter: Barak Korren
>Assignee: infra
>  Labels: first_time_task
>
> It may be the case that we don't need the 4.1 publisher jobs any more.
> Since those jobs are still in the old pre-CQ format where artifacts we 
> collected by the job itself, their existence makes the CI system's 
> maintenance harder...



--
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/CQ54UYRLXBJATDPNCONVFSOOURI57UUN/

[JIRA] (OVIRT-1996) Remove the 4.1 nightly publisher job

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-1996:

Epic Link: OVIRT-2044  (was: OVIRT-400)

> Remove the 4.1 nightly publisher job
> 
>
> Key: OVIRT-1996
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1996
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Publisher jobs
>Reporter: Barak Korren
>Assignee: infra
>  Labels: first_time_task
>
> It may be the case that we don't need the 4.1 publisher jobs any more.
> Since those jobs are still in the old pre-CQ format where artifacts we 
> collected by the job itself, their existence makes the CI system's 
> maintenance harder...



--
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/KQARKAUPDYZURKW6QSDMECEHWGRCPNS4/

[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base for STDCI

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-2001:

Epic Link:   (was: OVIRT-400)

> Create FAQ/Knowledge Base for STDCI
> ---
>
> Key: OVIRT-2001
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Barak Korren
>Assignee: infra
>  Labels: first_time_task
>
> There are many common use cases and issues in STDCI that could benefit from 
> case/task-specific documentation. So we should have a FAQ page or a Knowledge 
> Base about STDCI to cover these issues.
> Before we can make the page we need a critical mass (at least 3) of issues 
> and solutions, so we will use comments on this ticket to collect them as they 
> arise.



--
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/FUEQW2N63XTWOFLH2S67RGHYDH5BX2E3/

[JIRA] (OVIRT-2001) Create FAQ/Knowledge Base for STDCI

[Barak Korren (oVirt JIRA)]

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barak Korren updated OVIRT-2001:

Epic Link: (was: OVIRT-400)

> Create FAQ/Knowledge Base for STDCI
> ---
>
> Key: OVIRT-2001
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2001
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Barak Korren
>Assignee: infra
>  Labels: first_time_task
>
> There are many common use cases and issues in STDCI that could benefit from 
> case/task-specific documentation. So we should have a FAQ page or a Knowledge 
> Base about STDCI to cover these issues.
> Before we can make the page we need a critical mass (at least 3) of issues 
> and solutions, so we will use comments on this ticket to collect them as they 
> arise.



--
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/43PKPE63XJFL4CCJ77XDDZVV7TODNCYW/