This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
Runner resilience part 1/N: startup resilience to server being down or going down #3087
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.
This is the first body of work towards making runners more resilient to servers being down (and ultimately vice versa). This part focuses on the server going down or already being down during the runner startup process.
This PR makes the runner able to tolerate the following conditions:
Prior to this PR, all four scenarios above would crash or exit the runner.
All four scenarios are unit tested.
This PR does not improve runner resilience with regards to job execution. That is a future PR.