Hi Dan,
- Original Message -
> From: "Dan Callaghan"
> To: "Beaker Devel"
> Cc: "Min Shin"
> Sent: Wednesday, February 6, 2013 5:59:51 PM
> Subject: Re: Defining a harness API
>
> Excerpts from Dan Callaghan's message of 2012-12-20 14:50:15 +1000:
> > First sketch of an HTTP API below.
Excerpts from Dan Callaghan's message of 2012-12-20 14:50:15 +1000:
> First sketch of an HTTP API below. I don't think I've forgotten
> anything...
I've just uploaded a patch series to Gerrit which implements most of
this draft API:
http://gerrit.beaker-project.org/1703
http://gerrit.be
On 01/03/2013 11:27 PM, Bill Peck wrote:
On 01/02/2013 07:40 PM, Dan Callaghan wrote:
I think right now if the harness stops a task without recording any
results then it will just become Completed/New, which might be
reasonable if the harness doesn't want to say whether the task passed or
failed
On 01/02/2013 07:40 PM, Dan Callaghan wrote:
Excerpts from Nick Coghlan's message of 2013-01-02 11:53:20 +1000:
On 12/21/2012 12:52 PM, Raymond Mancy wrote:
* report results and upload logs
I don't think results should be a necessity. I wonder if the LC should only
require the API to expose a
Excerpts from Nick Coghlan's message of 2013-01-02 11:53:20 +1000:
> On 12/21/2012 12:52 PM, Raymond Mancy wrote:
> >> * report results and upload logs
> >
> > I don't think results should be a necessity. I wonder if the LC should only
> > require the API to expose a way of setting the status of a
On 12/21/2012 12:52 PM, Raymond Mancy wrote:
* report results and upload logs
I don't think results should be a necessity. I wonder if the LC should only
require the API to expose a way of setting the status of a task. e.g.
Running/Completed.
Because the UI of beaker is pretty tightly coupled
- Original Message -
> From: "Dan Callaghan"
> To: "Beaker Devel"
> Sent: Wednesday, December 19, 2012 4:46:19 PM
> Subject: [Beaker-devel] Defining a harness API
>
> An important first step towards supporting alternative harnesses
> and/o
Excerpts from Bill Peck's message of 2012-12-20 22:51:06 +1000:
> On 12/19/2012 11:50 PM, Dan Callaghan wrote:
> > First sketch of an HTTP API below. I don't think I've forgotten
> > anything...
>
> Hi Dan,
>
> What if a group wants to use an alternate harness? Is the idea that the
> alternate
On 12/19/2012 11:50 PM, Dan Callaghan wrote:
First sketch of an HTTP API below. I don't think I've forgotten
anything...
Hi Dan,
What if a group wants to use an alternate harness? Is the idea that the
alternate harness provide a backend plugin which would use this API? or
would we be free
First sketch of an HTTP API below. I don't think I've forgotten
anything...
Excerpts from Dan Callaghan's message of 2012-12-19 16:46:19 +1000:
> There are four areas the API needs to cover (that I can think of). The
> harness needs to be able to:
>
> * find out what to run
Get recipe XML:
An important first step towards supporting alternative harnesses and/or
the mythical Beaker Simple Harness is coming up with a stable,
documented API for the harness to interact with Beaker. So I'm starting
this thread now to get the ball rolling.
My first thoughts:
* It should have the smalle
11 matches
Mail list logo
