ci: fetch stable/dev releases using helm show to avoid cache issues #3256
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously we fetched the latest stable and dev release from metadata we have maintained, but doing that and then using `helm install` of that version made us use two sources of data, where one could be relatively outdated due to hitting a cache while the other may not. Using `helm show`, we rely on the helm chart repository website returning a index.yaml listing versions etc both when checking whats the latest versions, and when installing - like that we avoid a cache issue I think.
consideRatio
force-pushed
the
pr/avoid-cache-issues
branch
from
1d08d6f
to
4060b6a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sibling PR to jupyterhub/binderhub#1785