Excerpts from Nick Coghlan's message of 2013-11-11 16:28:43 +1000:

Since I've been reviewing and working on a couple of beah and rhts changes recently, it occurred to me it would be highly desirable to have some kind of CI for harness related updates.

However, I also can't see a straightforward way to make that happen :(

For beah, a script could: * produce a build * create a yum repo from that build and put it somewhere * run a job (containing what tasks?) with <repo name="beaker-harness-under-test" url="SOMEWHERE" /> and the beah build will be picked up, assuming its RPM NVR is higher than whatever is available on the Beaker server where the job is running

For rhts, no. It needs to just become part of beah anyway.