[Beaker-devel] Beaker tasks in a separate repository?

Nick Coghlan ncoghlan at redhat.com
Fri Nov 1 02:50:51 UTC 2013


On 10/31/2013 08:20 PM, Ales Zelinka wrote:
> On 31.10.2013 05:19, Amit Saha wrote:
>> I am beginning to think why don't we maintain the Beaker tasks in a
>> separate repository?
>> Each task has and will have their own version/release info, so there
>> won't be a "release"
>> of the tasks per se.
>>
>> We have made task upgrades in the past at various points during the
>> release cycle, so there
>> doesn't seem to be any pressing reason not to do this.
>>
>> Thoughts?
>>
>> Best,
>> -Amit.
>>
> Hi,
> what about tasks installing other tasks? I.e. some kind of setup task
> doing "yum install 'test(/some/other/task)'?

Sorry, repository was a bit ambiguous there - Amit was asking about the
git repositories on beaker-project.org, not the harness or task library
yum repos in a Beaker installation.

At the moment, the source code for the standard tasks is in the main
Beaker repo, which means they appear to be coupled directly to the
versioning of Beaker itself, when they're generally quite independent
(new versions of the tasks could theoretically have a higher minimum
required version of Beaker or the test harness, but upgrading the Beaker
server components definitely shouldn't break the old task versions).

Since we're looking at properly publishing the source for the virt
tasks, it makes sense to split out the other (relatively) version
independent tasks from the main Beaker repo first.

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