Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
health api: expose
GET /_health_report
with pipelines/*/status probe #16398health api: expose
GET /_health_report
with pipelines/*/status probe #16398Changes from 2 commits
25c7262
25083d6
e7dc66c
11fe7c1
b6cc58e
bcb0563
db6017c
aa6ede4
dba08e0
3dfd857
aaede5b
c96baaf
34a7d64
5c4a035
e7b1f39
05e858f
deba3f8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had thought we could rely on the difference between
finished_run
andfinished_execution
to tell us whether we had crashed, becausefinished_run
is only set in a non-exceptional path, but it turns out that the execeptions from a crash are already handled by the time it gets there.Ideally we would have a finite state machine for the possible states of a given pipeline instead of having state sprinkled throughout, but that task was a much larger lift than simply adding a single flag.
I found a dirty way to abuse the ruby filter to cause an exception that escapes its handling and causes the pipeline to crash, emulating the type of crash that is possible by a plugin that fails to handle exceptions: