linaro-release team mailing list archive

[Alexander Sack <asac@xxxxxxxxxx>]

On Tue, Sep 6, 2011 at 5:40 PM, Paul Sokolovsky
<842452@xxxxxxxxxxxxxxxxxx>wrote:

> On Tue, 06 Sep 2011 13:24:49 -0000
> Alexander Sack <asac@xxxxxxxxxx> wrote:
>
> > On Tue, Sep 6, 2011 at 2:24 PM, Frans Gifford
> > <frans.gifford@xxxxxxxxxx>wrote:
> >
> > > Feel free to mark as invalid if you think this is the correct
> > > behaviour.
> > >
> > >
> > maybe a third state: SUCCESSWITHPROBLEMS would be another option? Not
> > sure how easy that is to do on jenkins. I guess this stuff ultimately
> > needs to be visualized on a lava dashboard with info like: build,
> > lava submission, boot, tests etc. in one shot.
>
> Actually, Jenkins exactly has those standard states: success, build
> failed (failure), build succeeded, but tests failed (unstable). It's
> just we don't use Jenkins right, so not clear how easy it would be to
> do that quickly.
>
>
I think exporting build and test success/fail states through jenkins would
be "nice to have" :).

-- 

 - Alexander