Hi Bill, Hi Kevin,
1. recipes contain task's _RPM_ name and _yum_ is expected to install
It is easy to understand this Fedora-centric functionality: we are
primary users of the tool.
2. Beaker is supposed to be used with _Windows_ machines too, to test
e.g. JBoss, virtualization,...
Is this rpm+yum approach portable to Windows?
I have heard of cygwin, but let's keep the interface independent - in
sake of modularity, extensibility, [ insert any other buzzword here... ;-) ]
What about using env.variable and executable in task instead of rpm tag:
- <rpm name="rh-tests-examples-testargs.noarch"/>
+ <param name="RPMPACKAGE" value="rh-tests-examples-testargs.noarch"/>
+ <executable url="http://host.name.org/path/to/executable"/>
The executable tag could take optional positional arguments - arg tag.
The url argument is URL of a task-adaptor (e.g. rhts-task-adaptor).
In our case it will:
- set-up yum repository
- download and install a test-file
- run the test-file,
...which in case of RHTS tests means:
- set the environment - e.g. RESULT_SERVER
- run the task (make run in this case)
- capture XML-RPC calls and
- and report events back to Harness