Implementation tracking issue for http://beaker-project.org/dev/proposals/external-tasks.html Concerns/questions still to be addressed: 1. Changing from indicating external tasks by a NULL task reference to using an explicit "external" column in the task library. There will be a default entry used for any tasks that reference an external task without also providing a task name. 2. Whether or not to make the default task entry one that actually retrieves a task via git and runs it in the default harness, rather than requiring the use of a harness other than beah to take advantage of this feature.
http://gerrit.beaker-project.org/2817 http://gerrit.beaker-project.org/2821
This can be retested once bug 576304 is VERIFIED.
verified on beaker-devel(Beaker 0.15.6.git.133.bf56afa)-->pass steps: 1. set ks_meta="harness=restraint", 2. set <repo name="beaker-restaint" url="http://file.bos.redhat.com/~bpeck/restraint/el6eso--test/"/> 3. add external task in the job xml and submit the job. 4. check the results according to the doc in comment0: 1.) testing external task in job submitted xml.-->pass 2.) testing external task in job results XML.-->pass 3.) testing Fetching tasks from the Url-->pass Additional feature: 4.) testing the versions which displayed with the recipe results in Beaker’s web UI and included in the job results XML.-->pass, since beah use the same Api which has been tested in bug 576304.
Beaker 0.16.0 has been released.
*** Bug 961277 has been marked as a duplicate of this bug. ***
For the benefit of those that end up here after trying to use this feature with the default beah harness and finding that it doesn't work, that's because *beah* doesn't support this feature (and likely never will - providing support for this feature by default would likely mean replacing beah with something else as the default harness). Instead, the external tasks feature is designed to allow alternative harnesses to bypass Beaker's task library if they choose. One such harness is https://github.com/p3ck/restraint/ (which includes instructions on how to use it to run tests both standalone and in Beaker)