[Beaker-devel] Separate git repo and release process for standard tasks

Nick Coghlan ncoghlan at redhat.com
Mon Nov 11 01:21:35 UTC 2013


Amit has been looking at creating separate documentation for the default
test harness, and that will eventually lead to a separate release
process for the harness as well (allowing harness updates to be more
easily published without publishing a new Beaker release). This becomes
more significant as we start more actively supporting multiple Beaker
installations which may be running different versions of Beaker, and
also as we start maintaining multiple active branches in the Beaker repo
(at the moment, that's two maintenance branches and the develop branch,
although we expect the normal case to just be one maintenance branch and
the develop branch).

A related problem exists with the Tasks directory, especially as we
start looking to publish more of the current
Red-Hat-internal-for-no-good-reason utility tasks like
/distribution/virt/install, /distribution/virt/start and
/distribution/command.

The explicit "Library task" support in Beaker wizard discussed in
https://bugzilla.redhat.com/show_bug.cgi?id=910750 is also relevant, as
we're likely to end up wanting to publish some library tasks as open
source, and we're also going to want a home for the "reference tasks"
described in https://bugzilla.redhat.com/show_bug.cgi?id=961239

This suggests to me that over the next few weeks or months, we should
look at moving the existing open source tasks out of the main Beaker
repo into a new "beaker-tasks" repo, and structure the latter in a way
that makes it possible to install the "latest and greatest" Beaker tasks
into your instance by doing something like:


    $ sudo yum update beaker-tasks-core beaker-tasks-reference
beaker-tasks-library
    $ bkr update-standard-tasks core reference library

rather than the current:

    $ wget -r -np -nc https://beaker-project.org/tasks/
    $ for f in `ls *.rpm`
    > do
    >     bkr task-add --hub=http://beaker-server-lc.beaker/bkr \
    >     --username=<USER> --password=<PASSWORD> $f
    > done

Cheers,
Nick.

-- 
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane

Testing Solutions Team Lead
Beaker Development Lead (http://beaker-project.org/)


More information about the Beaker-devel mailing list