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

Barak Korren commented on OVIRT-1786:

the lack of configurability is by design – so that all suits have exactly the same “API”, and therefore we can easily use them in various places and no suit-specific knowledge is needed for running any suit.

I suggest you rethink your design so extra variables are not needed. Some options you can consider:

• Have the suit automatically test various different variable values internally (You can use the lago snapshot and restor features to to reset the system to a known state and re-test).

• Create multiple suites that share most code and predefine variable values (E.g. ‘Big'/'Medium’ and ‘Small’ suits).

Featue request: Pass env variables to the manual suite

     Key: OVIRT-1786
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1786
 Project: oVirt - virtualization made easy
         Issue Type: By-EMAIL
Reporter: Roy Golan
Assignee: infra

Hi, I need the ability to customize a running suite execution. I already do that today by exposing env variables to the performance suite, I just need an ability to create and pass that using the (great :) ) manual job. If you need more references just let me know Thanks

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