what is the current best way for a UX designer to verify a patch?
Hey, I'm unsure of the state of OST / Orb as far as a demo tool. I want a single push button operation so Liz can verify UI patches. Can we do that? Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme@redhat.com IRC: gshereme <https://red.ht/sig>
On Wed, Jun 6, 2018 at 6:34 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
Hey,
I'm unsure of the state of OST / Orb as far as a demo tool.
Orb is not a tool to verify patches, its an easy way to checkout oVirt fast and to experience the product ( replacing ovirt-live ), so I'm not sure it fits the need. To test any oVirt patch you need to do the following steps: 1. run 'ci please build' in the relevant patch on Gerrit ( I'm guessing most of the time it will be ovirt-engine or dashboard? ) 2. run the OST Manual job with the RPMs produced by the 'build-on-deman' job from step 1 ( which can be multiple projects/rpms as well ). This will allow verifying the patch, but not to login to the webadmin once its done, for that you will need to run OST locally and login to the instance afterwards. So instead of using the manual job you can run OST locally with the '-s' option and give the link to the jenkins job with the RPMs, then you can login to the webadmin afterwars and check the result. More info here: http://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/index....
I want a single push button operation so Liz can verify UI patches. Can we do that?
Its not a single push botton operation, but that the best available for now, any improvements will need to be discussed, designed, scoped, priorities as any other request to see its value vs development effort, etc... I suggest you'll schedule a meeting with Liz and Gal to do a short demo or discuss the needs in more depth if the above procedure is not trivial.
Best wishes, Greg
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
gshereme@redhat.com IRC: gshereme <https://red.ht/sig>
_______________________________________________ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-leave@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/FBU3PBB2JHCPNDB6YPZPEDWLK3NN4JIH/
-- 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)
On Thu, Jun 7, 2018 at 3:04 AM, Eyal Edri <eedri@redhat.com> wrote:
On Wed, Jun 6, 2018 at 6:34 PM, Greg Sheremeta <gshereme@redhat.com> wrote:
Hey,
I'm unsure of the state of OST / Orb as far as a demo tool.
Orb is not a tool to verify patches, its an easy way to checkout oVirt fast and to experience the product ( replacing ovirt-live ), so I'm not sure it fits the need. To test any oVirt patch you need to do the following steps:
1. run 'ci please build' in the relevant patch on Gerrit ( I'm guessing most of the time it will be ovirt-engine or dashboard? ) 2. run the OST Manual job with the RPMs produced by the 'build-on-deman' job from step 1 ( which can be multiple projects/rpms as well ).
This will allow verifying the patch, but not to login to the webadmin once its done, for that you will need to run OST locally and login to the instance afterwards. So instead of using the manual job you can run OST locally with the '-s' option and give the link to the jenkins job with the RPMs, then you can login to the webadmin afterwars and check the result.
More info here: http://ovirt-system-tests.readthedocs.io/en/ latest/CI/developers_info/index.html
I want a single push button operation so Liz can verify UI patches. Can we do that?
Its not a single push botton operation, but that the best available for now, any improvements will need to be discussed, designed, scoped, priorities as any other request to see its value vs development effort, etc...
I suggest you'll schedule a meeting with Liz and Gal to do a short demo or discuss the needs in more depth if the above procedure is not trivial.
Thanks for the writeup. I've indeed done this several times, and this is what I'll set Liz up with. I was just wondering if the creation of orb had made this closer to push button, but this is quite close. Thanks!
Best wishes, Greg
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
gshereme@redhat.com IRC: gshereme <https://red.ht/sig>
_______________________________________________ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/communit y/about/community-guidelines/ List Archives: https://lists.ovirt.org/archiv es/list/infra@ovirt.org/message/FBU3PBB2JHCPNDB6YPZPEDWLK3NN4JIH/
--
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)
-- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme@redhat.com IRC: gshereme <https://red.ht/sig>
participants (2)
-
Eyal Edri -
Greg Sheremeta