On Thu, Nov 10, 2011 at 4:32 PM, Michael Hudson-Doyle
<michael.hudson@linaro.org> wrote:
...
After all this thinking and typing I think I've come to some
conclusions:
1) There is a category of error where we should just stop. As far as I
know, this isn't really handled today.
2) There is another category of error where we should report failure,
but not execute any other actions. This makes me thing that having
'report results' as an action is a bit strange -- perhaps the
dashboard and bundle stream should really be directly in the job,
rather than an action?
ISTR we defined some exceptions in lava as being Fatal, or Non-Fatal - the idea being that there would be subclasses of those to add detail. That way we don't need to decide on every single error, just how far to pass it up before someone can take action on it. The fatal ones of course would be the ones where we just can't reasonably expect to proceed and gain anything from it (ex. image fails to deploy).
3) I need to write another, probably equally long, email about
dependencies between actions :-)