June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2221) Reposync builder will no work with DNF
by Gal Ben Haim (oVirt JIRA) 21 Jun '18

21 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2221?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2221: -------------------------------- Status: In Progress (was: To Do) > Reposync builder will no work with DNF > --------------------------------------- > > Key: OVIRT-2221 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2221 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > Part of the reposync builder tool is a Yum plugin which auto-generates the reposync-config with "includepkgs" field. > DNF doesn't support Yum plugins, so we will have to rewrite the plugin for DNF, -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2229) Automate updating of ovirt-engine-wildfly
by eyal edri (oVirt JIRA) 21 Jun '18

21 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2229?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2229: ---------------------------------- cc [~mwperina] we're looking into a way to automate the build of wildfly from their nightly builds. > Automate updating of ovirt-engine-wildfly > ----------------------------------------- > > Key: OVIRT-2229 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2229 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > > As an oVirt developer I want to test the oVirt source code against new versions of Wildfly as early as possible so that I can find issues early. > h3. Acceptance Criteria: > # Have a 'poll' job monitor for releases of Wildfly and update the ovirt-engine-wildfly source code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2229) Automate updating of ovirt-engine-wildfly
by Barak Korren (oVirt JIRA) 21 Jun '18

21 Jun '18

Barak Korren created OVIRT-2229: ----------------------------------- Summary: Automate updating of ovirt-engine-wildfly Key: OVIRT-2229 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2229 Project: oVirt - virtualization made easy Issue Type: New Feature Components: CI client projects Reporter: Barak Korren Assignee: infra As an oVirt developer I want to test the oVirt source code against new versions of Wildfly as early as possible so that I can find issues early. h3. Acceptance Criteria: # Have a 'poll' job monitor for releases of Wildfly and update the ovirt-engine-wildfly source code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2228) automating repoman deployment
by Emil Natan (oVirt JIRA) 21 Jun '18

21 Jun '18

Emil Natan created OVIRT-2228: --------------------------------- Summary: automating repoman deployment Key: OVIRT-2228 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2228 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Emil Natan Assignee: infra Automate repoman deployment using its own change-queue or a 'ci-tools' change-queue. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 280 - Failure!
by jenkins＠jenkins.phx.ovirt.org 21 Jun '18

21 Jun '18

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/280/ Build Number: 280 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #280 [Sandro Bonazzola] yum-repos: master: adjusted for new packages ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2227) Re: Push rights to vdsm
by eyal edri (oVirt JIRA) 21 Jun '18

21 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2227?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2227: ---------------------------------- [~ena(a)redhat.com] this request was to be able to send a patch to VDSM on Gerrit, not to trigger CI jobs on a patch. Sending patch to Gerrit can be done by any registered user of Gerrit ( anyone can register, even malicious users for that matter ), and that is why we have the whitelist in effect, so only approved users will be able to trigger jobs on the CI. Having said that, he will need to be added to the whitelist if he wants to run CI jobs, so maybe rename the ticket accordingly since the original issue was resolved AFAIK > Re: Push rights to vdsm > ----------------------- > > Key: OVIRT-2227 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2227 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Emil Natan > Assignee: infra > > Hi > You just need to ask one of the existing maintainers to send a patch to the > 'jenkins-whitelist' repo on gerrit.ovirt.org and > one of the infra members can merge it once it has +1 from an existing > maintainer. > I'm also adding 'infra-support' to open a ticket. > On Thu, Jun 21, 2018 at 11:14 AM, Tomasz Barański <tbaransk(a)redhat.com> > wrote: > > Eyal, > > > > Apparently I also need to be added to the CI whitelist. > > > > Tomo > > > > On 20.06.2018 12:49, Eyal Edri wrote: > > > > No worries, glad it works for you. > > Don't hesitate to reach out to infra again if you have any issues. > > > > On Wed, Jun 20, 2018 at 1:29 PM Tomasz Barański <tbaransk(a)redhat.com> > > wrote: > > > >> Eyal, > >> > >> I didn't set `username` in gerrit. Seems to have missed this step. > >> > >> It works now, sorry to bother you. > >> > >> Tomo > >> > >> On 20.06.2018 12:03, Eyal Edri wrote: > >> > >> Any registered user have push rights to new patches, did you follow the > >> guidelines on how to contribute to and oVirt project? > >> > >> https://ovirt.org/develop/dev-process/working-with-gerrit/ > >> > >> On Wed, Jun 20, 2018 at 1:00 PM Tomasz Barański <tbaransk(a)redhat.com> > >> wrote: > >> > >>> Hello, > >>> > >>> As a new Red Hatter, I need push right to `vdsm` project in oVirt's > >>> gerrit. > >>> > >>> Thank you > >>> Tomasz > >>> _______________________________________________ > >>> Infra mailing list -- infra(a)ovirt.org > >>> To unsubscribe send an email to infra-leave(a)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/2QDBTW4HH2FUGSQXHVDML5K3SIEAKIE2/ > >>> > >> > >> > >> -- > >> > >> Eyal edri > >> > >> > >> MANAGER > >> > >> RHV DevOps > >> > >> EMEA VIRTUALIZATION R&D > >> > >> > >> Red Hat EMEA <https://www.redhat.com/> > >> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > >> phone: +972-9-7692018 > >> irc: eedri (on #tlv #rhev-dev #rhev-integ) > >> > >> > >> > > > > -- > > > > Eyal edri > > > > > > MANAGER > > > > RHV DevOps > > > > EMEA VIRTUALIZATION R&D > > > > > > Red Hat EMEA <https://www.redhat.com/> > > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > > phone: +972-9-7692018 > > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > > > > > > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)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/F5LTNHLWRG4MLLBKMJQQGAOFDUGSPPCO/ > > > > > -- > Emil Natan > RHV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2227) Re: Push rights to vdsm
by Emil Natan (oVirt JIRA) 21 Jun '18

21 Jun '18

Emil Natan created OVIRT-2227: --------------------------------- Summary: Re: Push rights to vdsm Key: OVIRT-2227 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2227 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Emil Natan Assignee: infra Hi You just need to ask one of the existing maintainers to send a patch to the 'jenkins-whitelist' repo on gerrit.ovirt.org and one of the infra members can merge it once it has +1 from an existing maintainer. I'm also adding 'infra-support' to open a ticket. On Thu, Jun 21, 2018 at 11:14 AM, Tomasz Barański <tbaransk(a)redhat.com> wrote: > Eyal, > > Apparently I also need to be added to the CI whitelist. > > Tomo > > On 20.06.2018 12:49, Eyal Edri wrote: > > No worries, glad it works for you. > Don't hesitate to reach out to infra again if you have any issues. > > On Wed, Jun 20, 2018 at 1:29 PM Tomasz Barański <tbaransk(a)redhat.com> > wrote: > >> Eyal, >> >> I didn't set `username` in gerrit. Seems to have missed this step. >> >> It works now, sorry to bother you. >> >> Tomo >> >> On 20.06.2018 12:03, Eyal Edri wrote: >> >> Any registered user have push rights to new patches, did you follow the >> guidelines on how to contribute to and oVirt project? >> >> https://ovirt.org/develop/dev-process/working-with-gerrit/ >> >> On Wed, Jun 20, 2018 at 1:00 PM Tomasz Barański <tbaransk(a)redhat.com> >> wrote: >> >>> Hello, >>> >>> As a new Red Hatter, I need push right to `vdsm` project in oVirt's >>> gerrit. >>> >>> Thank you >>> Tomasz >>> _______________________________________________ >>> Infra mailing list -- infra(a)ovirt.org >>> To unsubscribe send an email to infra-leave(a)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/2QDBTW4HH2FUGSQXHVDML5K3SIEAKIE2/ >>> >> >> >> -- >> >> Eyal edri >> >> >> MANAGER >> >> RHV DevOps >> >> EMEA VIRTUALIZATION R&D >> >> >> Red Hat EMEA <https://www.redhat.com/> >> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >> phone: +972-9-7692018 >> irc: eedri (on #tlv #rhev-dev #rhev-integ) >> >> >> > > -- > > Eyal edri > > > MANAGER > > RHV DevOps > > EMEA VIRTUALIZATION R&D > > > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > > > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-leave(a)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/F5LTNHLWRG4MLLBKMJQQGAOFDUGSPPCO/ > > -- Emil Natan RHV DevOps -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

Push rights to vdsm
by Tomasz Barański 21 Jun '18

21 Jun '18

Hello, As a new Red Hatter, I need push right to `vdsm` project in oVirt's gerrit. Thank you Tomasz

3 5

[JIRA] (OVIRT-2226) Use nested stages to improve STDCI/CQ BlueOcean output
by Barak Korren (oVirt JIRA) 21 Jun '18

21 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2226?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2226: -------------------------------- Description: "Nested stages is something we wanted for a while, since without them its impossible to logically split apart operations that happen on the same node within a pipeline parallel branch. We were not the only ones to wat this, so this was tracked upstream in [JENKINS-38442|https://issues.jenkins-ci.org/browse/JENKINS-38442]\r\n\r\nA [PR|https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/227] implementing some support for this was finally merged into the [pipeline-model-definition-plugin|https://github.com/jenkinsci/pipeline-mode…] and included in the [1.3|https://github.com/jenkinsci/pipeline-model-definition-plugin/commits/p…] release.\r\n\r\nThe PR seems to indicate this may only be supported in the declarative pipeline syntax, so we'll need to check if this can also work with the iterative syntax or otherwise switch our code to the declarative syntax if possible." (was: Nested stages is something we wanted for a while, since without them its impossible to logically split apart operations that happen on the same node within a pipeline parallel branch. We were not the only ones to wat this, so this was tracked upstream in [JENKINS-38442|https://issues.jenkins-ci.org/browse/JENKINS-38442] A [PR|https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/227] implementing some support for this was finally merged into the [pipeline-model-definition-plugin|https://github.com/jenkinsci/pipeline-mode…] and included in the [1.3|https://github.com/jenkinsci/pipeline-model-definition-plugin/commits/p…] The PR seems to indicate this may only be supported in the declarative pipeline syntax, so we'll need to check if this can also work with the iterative syntax or otherwise switch our code to the declarative syntax if possible.) > Use nested stages to improve STDCI/CQ BlueOcean output > ------------------------------------------------------ > > Key: OVIRT-2226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2226 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: Change Queue, Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: infra > > Nested stages is something we wanted for a while, since without them its impossible to logically split apart operations that happen on the same node within a pipeline parallel branch. We were not the only ones to wat this, so this was tracked upstream in [JENKINS-38442|https://issues.jenkins-ci.org/browse/JENKINS-38442] > A [PR|https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/227] implementing some support for this was finally merged into the [pipeline-model-definition-plugin|https://github.com/jenkinsci/pipeline-mode…] and included in the [1.3|https://github.com/jenkinsci/pipeline-model-definition-plugin/commits/p…] release. > The PR seems to indicate this may only be supported in the declarative pipeline syntax, so we'll need to check if this can also work with the iterative syntax or otherwise switch our code to the declarative syntax if possible. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2226) Use nested stages to improve STDCI/CQ BlueOcean output
by Barak Korren (oVirt JIRA) 21 Jun '18

21 Jun '18

Barak Korren created OVIRT-2226: ----------------------------------- Summary: Use nested stages to improve STDCI/CQ BlueOcean output Key: OVIRT-2226 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2226 Project: oVirt - virtualization made easy Issue Type: Epic Components: Change Queue, Standard CI (Pipelines) Reporter: Barak Korren Assignee: infra Nested stages is something we wanted for a while, since without them its impossible to logically split apart operations that happen on the same node within a pipeline parallel branch. We were not the only ones to wat this, so this was tracked upstream in [JENKINS-38442|https://issues.jenkins-ci.org/browse/JENKINS-38442] A [PR|https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/227] implementing some support for this was finally merged into the [pipeline-model-definition-plugin|https://github.com/jenkinsci/pipeline-mode…] and included in the [1.3|https://github.com/jenkinsci/pipeline-model-definition-plugin/commits/p…] The PR seems to indicate this may only be supported in the declarative pipeline syntax, so we'll need to check if this can also work with the iterative syntax or otherwise switch our code to the declarative syntax if possible. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0