Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error handler failure reason as context data #248

Closed
gschueler opened this issue Dec 19, 2012 · 1 comment
Closed

Error handler failure reason as context data #248

gschueler opened this issue Dec 19, 2012 · 1 comment
Assignees
Milestone

Comments

@gschueler
Copy link
Member

Make context data available to error handlers that includes the reason for failure of the step.

context data:

  • result.reason
  • result.message
  • result.resultCode (executions)

Examples of "result.reason" values:

  • NonZeroResultCode (command execution)
  • HostNotFound (remote node can't be contacted)
  • ConnectionTimeout
  • etc
@gschueler
Copy link
Member Author

job reference arguments do not include expanded reason context data.

e.g. job reference as error handler, args "-message ${result.reason}", the result.reason is not expanded when the error handler is executed.

gschueler added a commit that referenced this issue Feb 20, 2013
for node dispatch failure reason data

issue #248
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant