We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Current thought is to not fail the step but add the output calculation failure to the step error.
The text was updated successfully, but these errors were encountered:
We have a list of questions at this point.
When error ignore true is on, how do we handle these cases:
output
throw
loop
retry
Same question probably applies for when retry { } should be used ... does it apply to the things above?
retry { }
Tagging @johnsmyth, @cbruno10 & @e-gineer
Sorry, something went wrong.
There are three types of errors in a pipeline run:
Evaluation errors always fail the step immediately and completely. The retry and error block settings are ignored.
Unexpected and runtime errors are handled by the user and their pipeline definition. They respect retry and error block settings for the step.
In the future we could add a new property to the error and retry blocks to optionally handle evaluation errors.
7e867a9
Added "if" attribute functionality to the error block. Refactored err…
eb04162
…or handling to ensure that it matches specification in issue #419. (#479)
vhadianto
No branches or pull requests
Current thought is to not fail the step but add the output calculation failure to the step error.
The text was updated successfully, but these errors were encountered: