[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35437#comment-35437 ]

eyal edri commented on OVIRT-1788:

I'm not sure why it will be better to maintain a new RPM rather than consuming all the RPMs needed from maintained repos from CentOS.. the only issue is to install multiple version of the same rpm, maybe using virtualenv?

Another alternative which will be simplest is to add a new std-ci project called ‘ovirt-ui-test-dependencies’ or something similar and there you can build a new RPM in build-artifacts which will get into OST/CQ flow as any other project.

new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium

     Key: OVIRT-1788
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788
 Project: oVirt - virtualization made easy
         Issue Type: Improvement
         Components: OST
Reporter: Greg Sheremeta
Assignee: infra

I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)

— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)