[Beaker-devel] API design for harness independent system reservations
Nick Coghlan
ncoghlan at redhat.com
Fri May 16 06:16:43 UTC 2014
On 05/16/2014 11:04 AM, Dan Callaghan wrote:
> Since this particular part of the feature (selecting when to reserve) is
> proving quite contentious I suggest that we start out implementing the
> simplest possible thing: if <reservesys/> is given, reserve
> unconditionally after all tasks are finished.
>
> Or we could do the next simplest thing:
>
> <reservesys/> reserve unconditionally
> <reservesys onpass="false"/> reserve if there is any result besides Pass
>
> This matches the current functionality of /distribution/reservesys with
> RESERVE_IF_FAIL=1.
Yeah, that sounds reasonable to me.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Hosted & Shared Services
Software Engineering & Development, Brisbane
Testing Solutions Team Lead
More information about the Beaker-devel
mailing list