- Infra - oVirt List Archives

[JIRA] (OVIRT-1528) Create a new oVirt_DR_site_to_site gerrit repository in gerrit.ovirt.org
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1528?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1528: -------------------------------- Epic Link: OVIRT-403 > Create a new oVirt_DR_site_to_site gerrit repository in gerrit.ovirt.org > ------------------------------------------------------------------------ > > Key: OVIRT-1528 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1528 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Gerrit/git > Reporter: Maor Lipchuk > Assignee: infra > > Hi all, > I would like to create a new repository in our gerrit.ovirt.org which > will include a tool to support DR solution for oVirt (see [1]) > Currently it is being developed on my personal github account (see > [2]), but once it will be migrated to be managed in gerrit.ovirt.org > it could be great since I can add it a standard CI tests. > [1] https://docs.google.com/document/d/1tMbTVvcS8wKW4c1V_Ee754bFtqRwl2fkPBNDXHp… > [2] https://github.com/maorlipchuk/ansible_ovirt_DR > Thanks, > Maor -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7547 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Jul '17

12 Jul '17

------=_Part_475_1021523201.1499854351483 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7547/, Build Number: 7547, Build Status: FAILURE ------=_Part_475_1021523201.1499854351483--

1 6

[JIRA] (OVIRT-1530) add upstream rebase to all OST jobs
by Gil Shinar (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1530?page=com.atlassian.jira.… ] Gil Shinar reassigned OVIRT-1530: --------------------------------- Assignee: Gil Shinar (was: infra) > add upstream rebase to all OST jobs > ----------------------------------- > > Key: OVIRT-1530 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1530 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Gil Shinar > > OST jobs, obviously do not use the standard stages builder and at the moment, do not run the upstream rebase script -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1530) add upstream rebase to all OST jobs
by Gil Shinar (oVirt JIRA) 12 Jul '17

12 Jul '17

Gil Shinar created OVIRT-1530: --------------------------------- Summary: add upstream rebase to all OST jobs Key: OVIRT-1530 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1530 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra OST jobs, obviously do not use the standard stages builder and at the moment, do not run the upstream rebase script -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1529) Gerrit reviewer plugin adds all reviewers even to draft patches
by Martin Sivak (oVirt JIRA) 12 Jul '17

12 Jul '17

Martin Sivak created OVIRT-1529: ----------------------------------- Summary: Gerrit reviewer plugin adds all reviewers even to draft patches Key: OVIRT-1529 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1529 Project: oVirt - virtualization made easy Issue Type: Bug Components: Gerrit/git Reporter: Martin Sivak Assignee: infra Draft versions of patches are supposed to be private and visible only to hand selected people. The reviewer plugin effectively kills draft status of the patch by assigning all relevant people to it. I would expect auto-reviewer rules are only applied upon publishing a draft patch. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1528) Create a new oVirt_DR_site_to_site gerrit repository in gerrit.ovirt.org
by Maor Lipchuk (oVirt JIRA) 12 Jul '17

12 Jul '17

Maor Lipchuk created OVIRT-1528: ----------------------------------- Summary: Create a new oVirt_DR_site_to_site gerrit repository in gerrit.ovirt.org Key: OVIRT-1528 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1528 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Maor Lipchuk Assignee: infra Hi all, I would like to create a new repository in our gerrit.ovirt.org which will include a tool to support DR solution for oVirt (see [1]) Currently it is being developed on my personal github account (see [2]), but once it will be migrated to be managed in gerrit.ovirt.org it could be great since I can add it a standard CI tests. [1] https://docs.google.com/document/d/1tMbTVvcS8wKW4c1V_Ee754bFtqRwl2fkPBNDXHp… [2] https://github.com/maorlipchuk/ansible_ovirt_DR Thanks, Maor -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

Create a new oVirt_DR_site_to_site gerrit repository in gerrit.ovirt.org
by Maor Lipchuk 12 Jul '17

12 Jul '17

Hi all, I would like to create a new repository in our gerrit.ovirt.org which will include a tool to support DR solution for oVirt (see [1]) Currently it is being developed on my personal github account (see [2]), but once it will be migrated to be managed in gerrit.ovirt.org it could be great since I can add it a standard CI tests. [1] https://docs.google.com/document/d/1tMbTVvcS8wKW4c1V_Ee754bFtqRwl2fkPBNDXHp… [2] https://github.com/maorlipchuk/ansible_ovirt_DR Thanks, Maor

1 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #3415 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Jul '17

12 Jul '17

------=_Part_500_198884145.1499870952872 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/3415/ Build Name: 3415 ovirt-engine-extension-aaa-jdbc (4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/79350 - title: packaging: Post release 1.1.6-1 - project: ovirt-engine-extension-aaa-jdbc - branch: master - author: Martin Pe=C5=99ina <mperina(a)redhat.com> ------=_Part_500_198884145.1499870952872--

1 0

[oVirt Jenkins] standard-enqueue - Build #2593 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Jul '17

12 Jul '17

------=_Part_498_475261101.1499870674181 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Build: http://jenkins.ovirt.org/job/standard-enqueue/2593/ Build Name: 2593 ovirt-engine-extension-aaa-jdbc (4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/79350 - title: packaging: Post release 1.1.6-1 - project: ovirt-engine-extension-aaa-jdbc - branch: master - author: Martin Pe=C5=99ina <mperina(a)redhat.com> ------=_Part_498_475261101.1499870674181--

1 0

[JIRA] (OVIRT-1527) Make Change-Id clickable
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1527?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1527: -------------------------------- Component/s: Gerrit/git Epic Link: OVIRT-403 Resolution: Fixed > Make Change-Id clickable > ------------------------ > > Key: OVIRT-1527 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1527 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Yedidyah Bar David > Assignee: infra > Priority: Low > > In openstack's gerrit, e.g. [1], the "Change-Id:" in the commit > message is clickable, and pressing it searches for patches including > it (e.g. in other branches). Might be useful for oVirt too. > [1] https://review.openstack.org/471802 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1527) Make Change-Id clickable
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1527?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1527: -------------------------------- Epic Link: OVIRT-403 > Make Change-Id clickable > ------------------------ > > Key: OVIRT-1527 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1527 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Yedidyah Bar David > Assignee: infra > Priority: Low > > In openstack's gerrit, e.g. [1], the "Change-Id:" in the commit > message is clickable, and pressing it searches for patches including > it (e.g. in other branches). Might be useful for oVirt too. > [1] https://review.openstack.org/471802 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1527) Make Change-Id clickable
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1527?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1527: -------------------------------- Priority: Low (was: Medium) > Make Change-Id clickable > ------------------------ > > Key: OVIRT-1527 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1527 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Yedidyah Bar David > Assignee: infra > Priority: Low > > In openstack's gerrit, e.g. [1], the "Change-Id:" in the commit > message is clickable, and pressing it searches for patches including > it (e.g. in other branches). Might be useful for oVirt too. > [1] https://review.openstack.org/471802 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1527) Make Change-Id clickable
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1527?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1527: -------------------------------- Issue Type: New Feature (was: By-EMAIL) > Make Change-Id clickable > ------------------------ > > Key: OVIRT-1527 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1527 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Yedidyah Bar David > Assignee: infra > > In openstack's gerrit, e.g. [1], the "Change-Id:" in the commit > message is clickable, and pressing it searches for patches including > it (e.g. in other branches). Might be useful for oVirt too. > [1] https://review.openstack.org/471802 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #3412 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Jul '17

12 Jul '17

------=_Part_493_338039835.1499868794003 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/3412/ Build Name: 3412 ovirt-engine-extension-aaa-jdbc (4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/79346 - title: packaging: packaging: Release 1.1.6-1 - project: ovirt-engine-extension-aaa-jdbc - branch: master - author: Martin Pe=C5=99ina <mperina(a)redhat.com> ------=_Part_493_338039835.1499868794003--

1 0

[oVirt Jenkins] standard-enqueue - Build #2590 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Jul '17

12 Jul '17

------=_Part_491_817089887.1499868441383 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Build: http://jenkins.ovirt.org/job/standard-enqueue/2590/ Build Name: 2590 ovirt-engine-extension-aaa-jdbc (4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/79346 - title: packaging: packaging: Release 1.1.6-1 - project: ovirt-engine-extension-aaa-jdbc - branch: master - author: Martin Pe=C5=99ina <mperina(a)redhat.com> ------=_Part_491_817089887.1499868441383--

1 0

[JIRA] (OVIRT-1527) Make Change-Id clickable
by Yedidyah Bar David (oVirt JIRA) 12 Jul '17

12 Jul '17

Yedidyah Bar David created OVIRT-1527: ----------------------------------------- Summary: Make Change-Id clickable Key: OVIRT-1527 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1527 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra In openstack's gerrit, e.g. [1], the "Change-Id:" in the commit message is clickable, and pressing it searches for patches including it (e.g. in other branches). Might be useful for oVirt too. [1] https://review.openstack.org/471802 -- Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1525) Automatically send welcome message on first push to gerrit
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1525?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1525: -------------------------------- Resolution: Duplicate (was: Fixed) Status: Done (was: To Do) > Automatically send welcome message on first push to gerrit > ---------------------------------------------------------- > > Key: OVIRT-1525 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1525 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Yedidyah Bar David > Assignee: infra > > Some weeks ago I pushed my first patch to openstack [1], and it > automatically added a reviewer called 'Welcome, new contributor' which > reviewed/commented (and so sent an email) with some introductory > material. Might be nice to have on oVirt's gerrit. > [1] https://review.openstack.org/471802 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1525) Automatically send welcome message on first push to gerrit
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1525?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1525: -------------------------------- Epic Link: OVIRT-400 Resolution: Fixed > Automatically send welcome message on first push to gerrit > ---------------------------------------------------------- > > Key: OVIRT-1525 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1525 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Yedidyah Bar David > Assignee: infra > > Some weeks ago I pushed my first patch to openstack [1], and it > automatically added a reviewer called 'Welcome, new contributor' which > reviewed/commented (and so sent an email) with some introductory > material. Might be nice to have on oVirt's gerrit. > [1] https://review.openstack.org/471802 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1525) Automatically send welcome message on first push to gerrit
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1525?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1525: -------------------------------- Epic Link: OVIRT-400 > Automatically send welcome message on first push to gerrit > ---------------------------------------------------------- > > Key: OVIRT-1525 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1525 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Yedidyah Bar David > Assignee: infra > > Some weeks ago I pushed my first patch to openstack [1], and it > automatically added a reviewer called 'Welcome, new contributor' which > reviewed/commented (and so sent an email) with some introductory > material. Might be nice to have on oVirt's gerrit. > [1] https://review.openstack.org/471802 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1525) Automatically send welcome message on first push to gerrit
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1525?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1525: -------------------------------- Component/s: oVirt CI > Automatically send welcome message on first push to gerrit > ---------------------------------------------------------- > > Key: OVIRT-1525 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1525 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Yedidyah Bar David > Assignee: infra > > Some weeks ago I pushed my first patch to openstack [1], and it > automatically added a reviewer called 'Welcome, new contributor' which > reviewed/commented (and so sent an email) with some introductory > material. Might be nice to have on oVirt's gerrit. > [1] https://review.openstack.org/471802 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1525) Automatically send welcome message on first push to gerrit
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1525?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1525: -------------------------------- Issue Type: New Feature (was: By-EMAIL) > Automatically send welcome message on first push to gerrit > ---------------------------------------------------------- > > Key: OVIRT-1525 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1525 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Yedidyah Bar David > Assignee: infra > > Some weeks ago I pushed my first patch to openstack [1], and it > automatically added a reviewer called 'Welcome, new contributor' which > reviewed/commented (and so sent an email) with some introductory > material. Might be nice to have on oVirt's gerrit. > [1] https://review.openstack.org/471802 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1525) Automatically send welcome message on first push to gerrit
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1525?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1525: ------------------------------------- This is a duplicate of OVIRT-1193 > Automatically send welcome message on first push to gerrit > ---------------------------------------------------------- > > Key: OVIRT-1525 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1525 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Some weeks ago I pushed my first patch to openstack [1], and it > automatically added a reviewer called 'Welcome, new contributor' which > reviewed/commented (and so sent an email) with some introductory > material. Might be nice to have on oVirt's gerrit. > [1] https://review.openstack.org/471802 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1526) Re-factor github std-CI job templates
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1526?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1526: ----------------------------------- Assignee: Barak Korren (was: infra) > Re-factor github std-CI job templates > ------------------------------------- > > Key: OVIRT-1526 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1526 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Low > Labels: standard-ci > > There are several issues with the YAML for the GiHUb job templates we currently have in '{{standard-stage.yaml}}': > # The 'check-patch' job has got a different template then the other jobs. This makes it harder to write project YAML files, And also very different from YAML files for Gerrit-based projects. > # Because of #1, the 'check-patch' jobs don't have any publishers defined. This makes them different from other STD-CI jobs that always have publishers that do things like collect and display test results. > Doing this is probably a prerequisite to OVIRT-1084 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1526) Re-factor github std-CI job templates
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

Barak Korren created OVIRT-1526: ----------------------------------- Summary: Re-factor github std-CI job templates Key: OVIRT-1526 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1526 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Priority: Low There are several issues with the YAML for the GiHUb job templates we currently have in '{{standard-stage.yaml}}': # The 'check-patch' job has got a different template then the other jobs. This makes it harder to write project YAML files, And also very different from YAML files for Gerrit-based projects. # Because of #1, the 'check-patch' jobs don't have any publishers defined. This makes them different from other STD-CI jobs that always have publishers that do things like collect and display test results. Doing this is probably a prerequisite to OVIRT-1084 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1526) Re-factor github std-CI job templates
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1526?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1526: -------------------------------- Epic Link: OVIRT-400 > Re-factor github std-CI job templates > ------------------------------------- > > Key: OVIRT-1526 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1526 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: Low > Labels: standard-ci > > There are several issues with the YAML for the GiHUb job templates we currently have in '{{standard-stage.yaml}}': > # The 'check-patch' job has got a different template then the other jobs. This makes it harder to write project YAML files, And also very different from YAML files for Gerrit-based projects. > # Because of #1, the 'check-patch' jobs don't have any publishers defined. This makes them different from other STD-CI jobs that always have publishers that do things like collect and display test results. > Doing this is probably a prerequisite to OVIRT-1084 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1525) Automatically send welcome message on first push to gerrit
by Yedidyah Bar David (oVirt JIRA) 12 Jul '17

12 Jul '17

Yedidyah Bar David created OVIRT-1525: ----------------------------------------- Summary: Automatically send welcome message on first push to gerrit Key: OVIRT-1525 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1525 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra Some weeks ago I pushed my first patch to openstack [1], and it automatically added a reviewer called 'Welcome, new contributor' which reviewed/commented (and so sent an email) with some introductory material. Might be nice to have on oVirt's gerrit. [1] https://review.openstack.org/471802 -- Didi -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1524) ovirt-release_4.1_check-patch-el7-x86_64 failing due to missing yum.conf
by Evgheni Dereveanchin (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1524?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1524: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > ovirt-release_4.1_check-patch-el7-x86_64 failing due to missing yum.conf > ------------------------------------------------------------------------ > > Key: OVIRT-1524 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1524 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > The [job|http://jenkins.ovirt.org/job/ovirt-release_4.1_check-patch-el7-x86_64/7…] recently started failing consistently with the following error: > + rm -f /etc/yum/yum.conf > + yum repolist enabled > CRITICAL:yum.cli:Config error: Error accessing file for config file:///etc/yum.conf > Related [test code|https://github.com/oVirt/ovirt-release/blob/master/automation/check-pa…] hasn't been changed recently, so maybe it is related to the new version of mock in use. Opening this to investigate the cause and possible solutions -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1524) ovirt-release_4.1_check-patch-el7-x86_64 failing due to missing yum.conf
by Evgheni Dereveanchin (oVirt JIRA) 12 Jul '17

12 Jul '17

Evgheni Dereveanchin created OVIRT-1524: ------------------------------------------- Summary: ovirt-release_4.1_check-patch-el7-x86_64 failing due to missing yum.conf Key: OVIRT-1524 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1524 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra The [job|http://jenkins.ovirt.org/job/ovirt-release_4.1_check-patch-el7-x86_64/7…] recently started failing consistently with the following error: + rm -f /etc/yum/yum.conf + yum repolist enabled CRITICAL:yum.cli:Config error: Error accessing file for config file:///etc/yum.conf Related [test code|https://github.com/oVirt/ovirt-release/blob/master/automation/check-pa…] hasn't been changed recently, so maybe it is related to the new version of mock in use. Opening this to investigate the cause and possible solutions -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-682) Improve CI logging and reporting to Gerrit (v2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-682: ------------------------------------ Gerrit trigger feedback configuration is not flexible enough to let us have each job customize the output it sends to Gerrit. Instead we will need to send the results to Gerrit ourselves with something like the GerritServer object (See [Gerrit 74874|https://gerrit.ovirt.org/#/c/74874/] But when sending results, the Gerrit trigger also calculates the votes for the flags by looking at all the jobs that it invoked. To do this ourselves we will need to be able to track all the checking scripts that are running in parallel for a given patchset, this probably means we have to implement OVIRT-1522 first. > Improve CI logging and reporting to Gerrit (v2) > ----------------------------------------------- > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: eedri > Assignee: infra > Priority: Low > Labels: standard-ci > > On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > Lately vdsm builds are failing in the install packages stage with > > this unhelpful error: > > > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > > 13:59:53 ERROR: Command failed. See logs for output. > > > > I downloaded the logs.tgz file from > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/artifact/exported-artifacts/logs.tgz > > > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > > root.log > > I found found this error: > > > > DEBUG util.py:421: Error: Package: > > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > > (ovirt-snapshot) > > DEBUG util.py:421: Requires: ioprocess = > > 0.17.0-1.201608111609.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.16.1-1.fc24.x86_64 (updates) > > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201607121058.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201608111129.gitbd272f2.fc24 > > > > So we have 2 issues here: > > > > 1. We need *all* errors in the console > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/console > Not sure its possible or easy to do, these errors usually come from mock > and are not relevant to the code running on the console. > I've cc'd infra-support and updated topic to track it and check our options. > Going foward, we might want to install a log collector like logstash and > then searching errors there should be much easier. > > > > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > > the missing ioprocess > > package. > > Maybe the project xml is not correct? > > > > Nir > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-682) Improve CI logging and reporting to Gerrit (v2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-682: ------------------------------- Summary: Improve CI logging and reporting to Gerrit (v2) (was: Improve CI logging) > Improve CI logging and reporting to Gerrit (v2) > ----------------------------------------------- > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: eedri > Assignee: infra > Priority: Low > Labels: standard-ci > > On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > Lately vdsm builds are failing in the install packages stage with > > this unhelpful error: > > > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > > 13:59:53 ERROR: Command failed. See logs for output. > > > > I downloaded the logs.tgz file from > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/artifact/exported-artifacts/logs.tgz > > > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > > root.log > > I found found this error: > > > > DEBUG util.py:421: Error: Package: > > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > > (ovirt-snapshot) > > DEBUG util.py:421: Requires: ioprocess = > > 0.17.0-1.201608111609.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.16.1-1.fc24.x86_64 (updates) > > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201607121058.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201608111129.gitbd272f2.fc24 > > > > So we have 2 issues here: > > > > 1. We need *all* errors in the console > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/console > Not sure its possible or easy to do, these errors usually come from mock > and are not relevant to the code running on the console. > I've cc'd infra-support and updated topic to track it and check our options. > Going foward, we might want to install a log collector like logstash and > then searching errors there should be much easier. > > > > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > > the missing ioprocess > > package. > > Maybe the project xml is not correct? > > > > Nir > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1523) Support multipile executors per CI stage (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1523?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1523: ------------------------------------- One quick and dirty way to achieve this that was suggested by [~nsoffer(a)redhat.com] and made possible by [Gerrit 79316|https://gerrit.ovirt.org/#/c/79316/] is to create "fake distributions" such as "el7:a" and "el7:b". This will allow people to use YAML to make jobs that target those fake distributions. Making such "fake distributions" is actually quite easy in practice since we got [Gerrit 73690|https://gerrit.ovirt.org/#/c/73690/] > Support multipile executors per CI stage (V2) > --------------------------------------------- > > Key: OVIRT-1523 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1523 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Currently we allow creating just one Jenkins "Free-Style" job per standard-CI stage and distribution. This means for e.g. that you can only have one "check-patch" script running on EL7 for a given project. > It had been requested several times to allow having multiple standard-CI scripts running in parallel on separate slaves as a means to get CI results faster. > Implementing this properly will probably require implementing both OVIRT-1522 and OVIRT-1013 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1523) Support multipile executors per CI stage (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

Barak Korren created OVIRT-1523: ----------------------------------- Summary: Support multipile executors per CI stage (V2) Key: OVIRT-1523 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1523 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Currently we allow creating just one Jenkins "Free-Style" job per standard-CI stage and distribution. This means for e.g. that you can only have one "check-patch" script running on EL7 for a given project. It had been requested several times to allow having multiple standard-CI scripts running in parallel on separate slaves as a means to get CI results faster. Implementing this properly will probably require implementing both OVIRT-1522 and OVIRT-1013 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1523) Support multipile executors per CI stage (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1523?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1523: -------------------------------- Epic Link: OVIRT-400 > Support multipile executors per CI stage (V2) > --------------------------------------------- > > Key: OVIRT-1523 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1523 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Currently we allow creating just one Jenkins "Free-Style" job per standard-CI stage and distribution. This means for e.g. that you can only have one "check-patch" script running on EL7 for a given project. > It had been requested several times to allow having multiple standard-CI scripts running in parallel on separate slaves as a means to get CI results faster. > Implementing this properly will probably require implementing both OVIRT-1522 and OVIRT-1013 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1522) Re-implement standard-CI with pipelines (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1522?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1522: -------------------------------- Epic Link: OVIRT-400 > Re-implement standard-CI with pipelines (V2) > -------------------------------------------- > > Key: OVIRT-1522 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1522 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The Standard-CI system job in Jenkins are currently implemented using "Free-Style" Jenkins jobs, if we could re-implement them with Jenkins pipelines, if will enable us to use cleaner code and also have many features that may be to hard to implement with "Free-Style" jobs. > Tickets that specify features that will probably require using pipelines will linkt to this ticket as a blocker. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1522) Re-implement standard-CI with pipelines (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

Barak Korren created OVIRT-1522: ----------------------------------- Summary: Re-implement standard-CI with pipelines (V2) Key: OVIRT-1522 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1522 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra The Standard-CI system job in Jenkins are currently implemented using "Free-Style" Jenkins jobs, if we could re-implement them with Jenkins pipelines, if will enable us to use cleaner code and also have many features that may be to hard to implement with "Free-Style" jobs. Tickets that specify features that will probably require using pipelines will linkt to this ticket as a blocker. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Summary: Automate standard-CI job creation (V2) (was: Automate standard-CI job creation) > Automate standard-CI job creation (V2) > -------------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. > But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. > The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: > 1. The platforms a certain project needs to be built and tested on. > 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. > We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1143) Standard CI V2
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1143: -------------------------------- Status: To Do (was: In Progress) > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > Labels: standard-ci > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1143) Standard CI V2
by eedri (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jira.… ] eedri updated OVIRT-1143: ------------------------- Fix Version/s: (was: OVIRT-INFRA-FEB-2017) > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > Labels: standard-ci > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1143) Standard CI V2
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jira.… ] Barak Korren reopened OVIRT-1143: --------------------------------- > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > Labels: standard-ci > Fix For: OVIRT-INFRA-FEB-2017 > > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1143) Standard CI V2
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1143: -------------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > Labels: standard-ci > Fix For: OVIRT-INFRA-FEB-2017 > > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1143) Standard CI V2
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1143: -------------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > Labels: standard-ci > Fix For: OVIRT-INFRA-FEB-2017 > > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1066) Fix error handling in the experimental flow Groovy script
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1066?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1066: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) 'experimental' is going to be replaced by the change-queue. > Fix error handling in the experimental flow Groovy script > --------------------------------------------------------- > > Key: OVIRT-1066 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1066 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Error handling is not done in a consistent manner in the Experimental flow Groovy script. Sometime exceptions are used, other times the 'currentBuild.result' variable is used and exceptions are actually suppressed. > This right way seems to be to use exceptions. Currently various things seem to be broken like properly marking that a build failed in the pipeline stage display plugin. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

Change in ci-info_env-inject[master]: asdasdasdasd asd
by review＠gerrit-staging.phx.ovirt.org 12 Jul '17

12 Jul '17

>From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has submitted this change and it was merged. ( https://gerrit-staging.phx.ovirt.org/63 ) Change subject: asdasdasdasd asd ...................................................................... asdasdasdasd asd Change-Id: Ia120f533910c1cfb1124e3a92f387e1c9be8cb30 --- M automation/check-patch.sh.el7 M automation/check-patch.sh.fc25 2 files changed, 12 insertions(+), 12 deletions(-) Approvals: Daniel Belenky: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/63 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: Ia120f533910c1cfb1124e3a92f387e1c9be8cb30 Gerrit-PatchSet: 1 Gerrit-Project: ci-info_env-inject Gerrit-Branch: master Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ci-info_env-inject[master]: asdasdasdasd asd
by review＠gerrit-staging.phx.ovirt.org 12 Jul '17

12 Jul '17

>From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/63 ) Change subject: asdasdasdasd asd ...................................................................... Patch Set 1: Continuous-Integration+1 Code-Review+2 Verified+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/63 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Ia120f533910c1cfb1124e3a92f387e1c9be8cb30 Gerrit-PatchSet: 1 Gerrit-Project: ci-info_env-inject Gerrit-Branch: master Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

Change in ci-info_env-inject[master]: asdasd
by review＠gerrit-staging.phx.ovirt.org 12 Jul '17

12 Jul '17

>From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has submitted this change and it was merged. ( https://gerrit-staging.phx.ovirt.org/62 ) Change subject: asdasd ...................................................................... asdasd Change-Id: I86efe6a1a6cf1f51cbd64783a5dccf07c2ba39a3 --- M automation/check-patch.sh.el7 M automation/check-patch.sh.fc25 2 files changed, 8 insertions(+), 8 deletions(-) Approvals: Daniel Belenky: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/62 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: I86efe6a1a6cf1f51cbd64783a5dccf07c2ba39a3 Gerrit-PatchSet: 1 Gerrit-Project: ci-info_env-inject Gerrit-Branch: master Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

1 0

Change in ci-info_env-inject[master]: asdasd
by review＠gerrit-staging.phx.ovirt.org 12 Jul '17

12 Jul '17

>From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/62 ) Change subject: asdasd ...................................................................... Patch Set 1: Continuous-Integration+1 Code-Review+2 Verified+1 -- To view, visit https://gerrit-staging.phx.ovirt.org/62 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I86efe6a1a6cf1f51cbd64783a5dccf07c2ba39a3 Gerrit-PatchSet: 1 Gerrit-Project: ci-info_env-inject Gerrit-Branch: master Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-HasComments: No

1 0

[oVirt Jenkins] standard-enqueue - Build #2581 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Jul '17

12 Jul '17

------=_Part_477_96828041.1499856226988 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Build: http://jenkins.ovirt.org/job/standard-enqueue/2581/ Build Name: 2581 ovirt-engine-extension-aaa-jdbc (4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/79318 - title: packaging: Fix FC24 repositories - project: ovirt-engine-extension-aaa-jdbc - branch: master - author: Martin Pe=C5=99ina <mperina(a)redhat.com> ------=_Part_477_96828041.1499856226988--

1 0

[CQ]: 79268, 5 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 12 Jul '17

12 Jul '17

Change 79268,5 (ovirt-engine-metrics) 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/79268/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1258/

2 1

[JIRA] (OVIRT-1468) Use CI mirrors for the slaves
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1468?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1468 at 7/12/17 11:52 AM: --------------------------------------------------------------- Here is an instance where this caused a failure in the CQ tester job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1254/consoleF… Here the 'upgrade-from-prevrelease-suit' didn't even reach the phase where it is running the OST. It is also quite hard to find this in the CQ/experimental test jobs. was (Author: bkorren(a)redhat.com) Here is an instance where this cause a failure in the CQ tester job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1254/consoleF… Here the 'upgrade-from-prevrelease-suit' didn't even reach the phase where it is running the OST. It is also quite hard to find this in the CQ/experimental test jobs. > Use CI mirrors for the slaves > ----------------------------- > > Key: OVIRT-1468 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1468 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: jenkins, mirrors, slaves > > Since we've seen that issues like OVIRT-1467 can very quickly break our entire infrastructure, it may be advisable to use out mirrors to isolate the slave VMs from the upstream repos as well, and not just the testing environments. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1468) Use CI mirrors for the slaves
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1468?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1468: ------------------------------------- Here is an instance where this cause a failure in the CQ tester job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1254/consoleF… Here the 'upgrade-from-prevrelease-suit' didn't even reach the phase where it is running the OST. It is also quite hard to find this in the CQ/experimental test jobs. > Use CI mirrors for the slaves > ----------------------------- > > Key: OVIRT-1468 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1468 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: jenkins, mirrors, slaves > > Since we've seen that issues like OVIRT-1467 can very quickly break our entire infrastructure, it may be advisable to use out mirrors to isolate the slave VMs from the upstream repos as well, and not just the testing environments. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0