[ovirt-devel] Re: what is the current best way for a UX designer to verify a patch?

On Wed, Jun 6, 2018 at 6:34 PM, Greg Sheremeta <gshereme(a)redhat.com&gt; wrote: 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/ind... 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. -- 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)