[ci] Update VM cache for each ES snapshot #205119
Open
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
Currently we're rebuilding our cache after the ES snapshot on main has been promoted. This makes an assumption that less frequent cache builds will save minutes over the chance of a build failure on main that will cause snapshots for all other passing branches to be out of date. That assumption hasn't been correct so far, so I'm moving the trigger to all branches.
jbudz
added
Team:Operations
|
Pinging @elastic/kibana-operations (Team:Operations) |
💚 Build Succeeded
Metrics [docs]
|
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.
Currently we're rebuilding our cache after the ES snapshot on main has been promoted. This makes an assumption that less frequent cache builds will save minutes over the chance of a build failure on main causing snapshots for all other passing branches to be out of date.
That assumption hasn't been correct so far, so I'm moving the trigger to all branches.