Use cf-rolling-restart over cf-recycle-plugin. #954
Merged
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.
Related to #943.
Rolling-restart is more recently maintained, is the original fork, and works with the latest CF CLI for when we upgrade.
It’s a bit of a shot-in-the-dark here since I don’t 100% understand what’s going on — the
cf-recycle-plugin
plugin isn’t correctly detecting process restarts. I had thought this was due to conflicting recycle jobs — one job was recycling a process out from the other — but since removing the concurrent jobs, the issue is not fixed.Looking at this morning’s run, the CircleCI job output seems to indicate that Instance 0 was never restarted, which caused the job to timeout. However, looking at the cell restart logs, we can see that it was correctly restarted:
This leads me to believe that this is an issue with the plugin — hence the PR. I’m pretty comfortable just trying something newer and seeing if it works, and moving on with our lives if it does. 🤷♂