RFC: Taskotron task description format
tflink at redhat.com
Fri Dec 6 00:21:47 UTC 2013
I've been working on this for a bit but finally have enough together
that we can start talking about the task description format for
The code to actually run tasks (well, task. for now, rpmlint is all
that's supported) is up at:
The runner code isn't very good yet but I didn't want to wait until it
was done before starting to discuss the task description format.
Continuing the use of rpmlint as an example, I have a task repository
set up on bitbucket:
At the moment, that task yaml file for rpmlint  looks like:
koji: download $envr
python: run_rpmlint.py $workdir
shell: clean $workdir
In a nutshell, the idea is to keep repetitive code out of the tasks
without requiring everything to be written in the same language or
porting the library to any language people want to use (perl, c, bash
The execution of the task is described in the yml file and eventually
delegates actual execution to the python file described in that yml
file. Output, for now, is in TAP format. The runner just spits it out
as text for the moment but eventually, that TAP output will be used for
reporting the results.
Items prepended with '$' represent variables - either things determined
at runtime (the working directory) or things that are arguments to the
specific task run (the envr of packages to check).
Examples of what future features could look like:
beaker: job=somejob.xml distro=$latestfedora
bodhi: download $updates
openstack: image=imagename config=someconfigtype size=m1.small
Any thoughts on whether this direction is a good direction to take or
suggestions on how the format could be improved? Eventually, I want to
send this out to devel@ for input but figured that the smaller group of
folks here would be a good start.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 490 bytes
Desc: not available
More information about the qa-devel