April 2017 - Infra - Ovirt List Archives

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6451 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

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

6 years, 12 months

1
48
0 / 0

[JIRA] (OVIRT-1213) Find a way to configure a real email addess for the Jenkins user in Gerrit

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1213?page=com.atlassian.jir... ] Evgheni Dereveanchin reassigned OVIRT-1213: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Find a way to configure a real email addess for the Jenkins user in Gerrit > -------------------------------------------------------------------------- > > Key: OVIRT-1213 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1213 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > The Jenkins user in Gerrit does no have a real emain configured for it. > We want it to have a real address so we can do things like setup a gravater for it, but if we setup an address it will get spammed with emails about each an evey comment added to each and every patch because Jenkins joins as a reviewer to all patches. > We need to find a way to make Gerrit not email Jenkins if it is a reviewer. This may help: > https://gerrit-review.googlesource.com/Documentation/user-notify.html -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

6 years, 12 months

1
0
0 / 0

[JIRA] (OVIRT-1223) Nightly/bare metal vdsm check-merged jobs

by danken (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1223?page=com.atlassian.jir... ] danken commented on OVIRT-1223: ------------------------------- spoken with Barak. He meant adding a new suit to OST. > Nightly/bare metal vdsm check-merged jobs > ----------------------------------------- > > Key: OVIRT-1223 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1223 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Leon Goldberg > Assignee: infra > Fix For: OVIRT-INFRA-MAR-2017 > > > Hey, > We're trying to come up with a solution to our lengthy check-merged > jobs, that are about to become even lengthier now when we've > discovered we're missing a permutation to our network tests. > check-merged currently takes roughly 50 minutes to run to completion, > with the network tests taking roughly 30 minutes; with the additional > permutation check-merged will run for more than an hour. > We thought of 2 possible solutions: > 1) Only run the additional permutation once a day (e.g. introduce a > nightly job). > 2) Run check-merged on bare metal -- network tests take roughly 1/3 of > the time on bare metal. > Somehow closing the gap to bare metal would also of course be nice. > We'd love your input. > Thanks, > Leon -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

6 years, 12 months

1
0
0 / 0

[JIRA] (OVIRT-1223) Nightly/bare metal vdsm check-merged jobs

by danken (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1223?page=com.atlassian.jir... ] danken commented on OVIRT-1223: ------------------------------- I don't really understand your suggestion. OST is all about system test. vdsm check-merged is about testing vdsm API. Do you suggest to pull in vdsm-tests onto host0 in OST, and run them there after OST finishes? Or do you suggest a completely new OST suit, dedicated to vdsm functional tests? > Nightly/bare metal vdsm check-merged jobs > ----------------------------------------- > > Key: OVIRT-1223 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1223 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Leon Goldberg > Assignee: infra > Fix For: OVIRT-INFRA-MAR-2017 > > > Hey, > We're trying to come up with a solution to our lengthy check-merged > jobs, that are about to become even lengthier now when we've > discovered we're missing a permutation to our network tests. > check-merged currently takes roughly 50 minutes to run to completion, > with the network tests taking roughly 30 minutes; with the additional > permutation check-merged will run for more than an hour. > We thought of 2 possible solutions: > 1) Only run the additional permutation once a day (e.g. introduce a > nightly job). > 2) Run check-merged on bare metal -- network tests take roughly 1/3 of > the time on bare metal. > Somehow closing the gap to bare metal would also of course be nice. > We'd love your input. > Thanks, > Leon -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

6 years, 12 months

1
0
0 / 0

[JIRA] (OVIRT-1354) SDK STD-CI jobs do not include pust-build cleanup steps

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1354?page=com.atlassian.jir... ] Barak Korren reassigned OVIRT-1354: ----------------------------------- Assignee: Barak Korren (was: infra) > SDK STD-CI jobs do not include pust-build cleanup steps > ------------------------------------------------------- > > Key: OVIRT-1354 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1354 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: Barak Korren > Priority: Highest > Labels: standard-ci > > The SDK STD-CI jobs have been defined using ther own strange YAML because of reasons that have to do with the names of the Git repos they are built from. > As a result a bug was introduced where the SDK jobs are created without cleanup steps. This ends up causing issues for other jobs shaving slaved with them. -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

6 years, 12 months

1
0
0 / 0

[JIRA] (OVIRT-1354) SDK STD-CI jobs do not include pust-build cleanup steps

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-1354: ----------------------------------- Summary: SDK STD-CI jobs do not include pust-build cleanup steps Key: OVIRT-1354 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1354 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: Highest The SDK STD-CI jobs have been defined using ther own strange YAML because of reasons that have to do with the names of the Git repos they are built from. As a result a bug was introduced where the SDK jobs are created without cleanup steps. This ends up causing issues for other jobs shaving slaved with them. -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

6 years, 12 months

1
0
0 / 0

[JIRA] (OVIRT-1354) SDK STD-CI jobs do not include pust-build cleanup steps

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1354?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1354: -------------------------------- Epic Link: OVIRT-400 > SDK STD-CI jobs do not include pust-build cleanup steps > ------------------------------------------------------- > > Key: OVIRT-1354 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1354 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Highest > Labels: standard-ci > > The SDK STD-CI jobs have been defined using ther own strange YAML because of reasons that have to do with the names of the Git repos they are built from. > As a result a bug was introduced where the SDK jobs are created without cleanup steps. This ends up causing issues for other jobs shaving slaved with them. -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

6 years, 12 months

1
0
0 / 0

[JIRA] (OVIRT-1353) Re: Jenkins Whitelist

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1353?page=com.atlassian.jir... ] Evgheni Dereveanchin updated OVIRT-1353: ---------------------------------------- Resolution: Done Status: Done (was: To Do) Merged, should work now. > Re: Jenkins Whitelist > --------------------- > > Key: OVIRT-1353 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1353 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > Adding infra-support to open a Jira ticket. > On 27 April 2017 at 12:21, Miroslava Voglova <mvoglova(a)redhat.com> wrote: > > Hi, > > > > I got this error: > > > > No Builds Executed > > > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/2... > > : To avoid overloading the infrastructure, a whitelist for > > running gerrit triggered jobs has been set in place, if > > you feel like you should be in it, please contact infra at > > ovirt dot org. > > > > Please can you add me to whitelist? > > > > Thanks, > > > > Mirka V. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

6 years, 12 months

1
0
0 / 0

[JIRA] (OVIRT-1353) Re: Jenkins Whitelist

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1353?page=com.atlassian.jir... ] Evgheni Dereveanchin commented on OVIRT-1353: --------------------------------------------- patch submitted for review > Re: Jenkins Whitelist > --------------------- > > Key: OVIRT-1353 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1353 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > Adding infra-support to open a Jira ticket. > On 27 April 2017 at 12:21, Miroslava Voglova <mvoglova(a)redhat.com> wrote: > > Hi, > > > > I got this error: > > > > No Builds Executed > > > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/2... > > : To avoid overloading the infrastructure, a whitelist for > > running gerrit triggered jobs has been set in place, if > > you feel like you should be in it, please contact infra at > > ovirt dot org. > > > > Please can you add me to whitelist? > > > > Thanks, > > > > Mirka V. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- This message was sent by Atlassian JIRA (v1000.910.0#100040)

6 years, 12 months

1
0
0 / 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #553 - FAILURE!

by jenkins＠jenkins.phx.ovirt.org

------=_Part_372_1460452815.1493290535410 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/553/ Build Name: 553 ovirt-engine-api-model (4.1) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/76125 - title: Adding docs for hostgroups service - project: ovirt-engine-api-model - branch: model_4.1 - author: Juan Hernandez <juan.hernandez(a)redhat.com> ------=_Part_372_1460452815.1493290535410--

6 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra April 2017