February 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1107) [gerrit hooks] don't update bug status to MODIFIED if there is an open patch of other gerrit instance
by Shlomo Ben David (oVirt JIRA) 05 Feb '17

05 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1107?page=com.atlassian.jira.… ] Shlomo Ben David reassigned OVIRT-1107: --------------------------------------- Assignee: Shlomo Ben David (was: infra) > [gerrit hooks] don't update bug status to MODIFIED if there is an open patch of other gerrit instance > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-1107 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1107 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: Shlomo Ben David > -- This message was sent by Atlassian JIRA (v1000.718.6#100026)

1 0

[JIRA] (OVIRT-1107) [gerrit hooks] don't update bug status to MODIFIED if there is an open patch of other gerrit instance
by Shlomo Ben David (oVirt JIRA) 05 Feb '17

05 Feb '17

Shlomo Ben David created OVIRT-1107: --------------------------------------- Summary: [gerrit hooks] don't update bug status to MODIFIED if there is an open patch of other gerrit instance Key: OVIRT-1107 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1107 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Shlomo Ben David Assignee: infra -- This message was sent by Atlassian JIRA (v1000.718.6#100026)

1 0

[JIRA] (OVIRT-1107) [gerrit hooks] don't update bug status to MODIFIED if there is an open patch of other gerrit instance
by Shlomo Ben David (oVirt JIRA) 05 Feb '17

05 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1107?page=com.atlassian.jira.… ] Shlomo Ben David updated OVIRT-1107: ------------------------------------ Epic Link: OVIRT-411 > [gerrit hooks] don't update bug status to MODIFIED if there is an open patch of other gerrit instance > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-1107 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1107 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.718.6#100026)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5127 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Feb '17

05 Feb '17

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

1 3

[JIRA] (OVIRT-1106) gerrit hooks should also handle 'Red Hat Enterprise Virtualization' bugs
by eyal edri [Administrator] (oVirt JIRA) 05 Feb '17

05 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1106?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1106: --------------------------------------------- Priority: High (was: Medium) > gerrit hooks should also handle 'Red Hat Enterprise Virtualization' bugs > ------------------------------------------------------------------------ > > Key: OVIRT-1106 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1106 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Until now the Gerrit Hooks only updated oVirt bugs, but on some occasions a patch have bug-url of a downstream bug, which should also be handled. > We should enable all available hooks we have on 'RHV' bugs as well, > specifically: > - add external tracker > - verify backport > - set POST > - set MODIFIED ( if the hook detects that another external tracker for internal gerrit instance is added, it shouldn't move to MODIFIED because the bug might need to wait for a d/s patch ) > The improvement for the modified hook should be done as a seperate task afte this one. -- This message was sent by Atlassian JIRA (v1000.718.6#100026)

1 0

[JIRA] (OVIRT-1106) gerrit hooks should also handle 'Red Hat Enterprise Virtualization' bugs
by eyal edri [Administrator] (oVirt JIRA) 05 Feb '17

05 Feb '17

eyal edri [Administrator] created OVIRT-1106: ------------------------------------------------ Summary: gerrit hooks should also handle 'Red Hat Enterprise Virtualization' bugs Key: OVIRT-1106 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1106 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra Until now the Gerrit Hooks only updated oVirt bugs, but on some occasions a patch have bug-url of a downstream bug, which should also be handled. We should enable all available hooks we have on 'RHV' bugs as well, specifically: - add external tracker - verify backport - set POST - set MODIFIED ( if the hook detects that another external tracker for internal gerrit instance is added, it shouldn't move to MODIFIED because the bug might need to wait for a d/s patch ) The improvement for the modified hook should be done as a seperate task afte this one. -- This message was sent by Atlassian JIRA (v1000.718.6#100026)

1 0

[JIRA] (OVIRT-1106) gerrit hooks should also handle 'Red Hat Enterprise Virtualization' bugs
by eyal edri [Administrator] (oVirt JIRA) 05 Feb '17

05 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1106?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1106: --------------------------------------------- Epic Link: OVIRT-411 > gerrit hooks should also handle 'Red Hat Enterprise Virtualization' bugs > ------------------------------------------------------------------------ > > Key: OVIRT-1106 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1106 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > Until now the Gerrit Hooks only updated oVirt bugs, but on some occasions a patch have bug-url of a downstream bug, which should also be handled. > We should enable all available hooks we have on 'RHV' bugs as well, > specifically: > - add external tracker > - verify backport > - set POST > - set MODIFIED ( if the hook detects that another external tracker for internal gerrit instance is added, it shouldn't move to MODIFIED because the bug might need to wait for a d/s patch ) > The improvement for the modified hook should be done as a seperate task afte this one. -- This message was sent by Atlassian JIRA (v1000.718.6#100026)

1 0

Re: [ovirt-devel] Question about testing
by Eyal Edri 05 Feb '17

05 Feb '17

On Sun, Feb 5, 2017 at 3:07 PM, Barak Korren <bkorren(a)redhat.com> wrote: > On 5 February 2017 at 14:58, Marc Young <3vilpenguin(a)gmail.com> wrote: > > I see emails floating around about Jenkins. > > > > Is there a public Jenkins, or possibly one that I can be invited to? > > I just finished the vagrant provider and pushed it to rubygems and am > > currently bringing up a new permanent oVirt server so that i can write > > some acceptance tests, but having access to a Jenkins and a testable > > oVirt setup would save me a ton of time. > > Yes, oVirt has Jenkins server, and a set of standards about how to > enable a project to use it [1]. > There is also the "oVirt Systems Tests" project [2] that knows how to > bring up a fully functional oVirt for testing purposes. > > Since you're project is on GitHub as opposed to oVirt's Gerrit, I'm > afraid it will have to wait a while until we can accomodate it, but > hopefully not for long [3]. > Adding Evgheni, the oVirt infra sys admin and the one who is also taking care of the Jenkins server. I'm also adding the 'infra(a)ovirt.org' which is the mailing list for the oVirt infra team ( the team who provides all CI/CD/Testing services for the oVirt project ). So we have our 'production' jenkins @ jenkins.ovirt.org where all oVirt projects are built & tested using the oVirt standard CI [1], as mentioned below, And we also have a staging jenkins [1] which is probably the best place to do tests on before deploying to the production instance. As for getting an oVirt instance up & running, its quite easy to do as Barak said, you just need to run any 'basic suite' from the ovirt-system-tests repository and you'll have a working oVirt running in less than 20 min on your laptop. More info on the OST doc page [2] [1] http://jenkins-staging.phx.ovirt.org/login?from=%2F [2] http://ovirt-system-tests.readthedocs.io/en/latest/docs/general/running_tes… > > [1]: http://ovirt-infra-docs.readthedocs.io/en/latest/CI/ > Build_and_test_standards.html > [2]: http://ovirt-system-tests.readthedocs.io/en/latest/ > [3]: https://ovirt-jira.atlassian.net/browse/OVIRT-970 > > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > > > -- 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)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5125 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 05 Feb '17

05 Feb '17

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

1 1

[JIRA] (OVIRT-1105) Re: Need a topic branch for experimental development
by Barak Korren (oVirt JIRA) 05 Feb '17

05 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1105?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1105: ------------------------------------- Can you think up of a name for it? Inventing names is hard... Also, for which project? I have to just assume you mean engine... > Re: Need a topic branch for experimental development > ---------------------------------------------------- > > Key: OVIRT-1105 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1105 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: infra > > Adding infra-support so a ticket will be opened > On Sun, Feb 5, 2017 at 1:17 PM, Roy Golan <rgolan(a)redhat.com> wrote: > > Hi infra, > > > > I want a new gerrit branch that will make it easier to collaborate with > > more developers on experimental, edgy changes. > > > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > -- This message was sent by Atlassian JIRA (v1000.718.6#100026)

1 0