Skip to content
This repository has been archived by the owner on Jun 15, 2024. It is now read-only.

Simplify way to get failed steps #163

Open
flosell opened this issue Feb 28, 2017 · 2 comments
Open

Simplify way to get failed steps #163

flosell opened this issue Feb 28, 2017 · 2 comments

Comments

@flosell
Copy link
Owner

flosell commented Feb 28, 2017

Follow up from #154:

It's a bit of an involved process getting information about failed steps, e.g. for slack notifications (https://gist.github.com/flosell/ff9976e9744814d60fcbb7d06f488f71). Maybe there should be code in LambdaCD itself to simplify this for users writing add-ons?

@thilo11
Copy link

thilo11 commented Feb 28, 2017

+1 I was facing similar challenges in lambdacd-junit. It would be great to have hooks maybe similar to those in GoCD?

@flosell
Copy link
Owner Author

flosell commented Mar 1, 2017

Thanks for the feedback @thilo11, however, I feel this is a slightly different use-case: What I meant with this issue was a way to get all failed steps in a pipeline when we get events via the event bus.

Your approach seems to be something that could be implemented with always-chaining which chains steps together inside a step and doesn't stop on failures. Even if inside the chain should be supported, giving you something that should be equivalent to GoCDs hooks:
https://github.com/flosell/lambdacd/blob/master/example/clj/todopipeline/steps.clj#L168-L174

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants