[CI] Cache ES snapshots on agents #132940
Merged
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
…to es-snapshot-cache
jbudz
approved these changes
May 25, 2022
brianseeders
added
release_note:skip
|
Pinging @elastic/kibana-operations (Team:Operations) |
brianseeders
added
v8.2.2
auto-backport
|
@elasticmachine merge upstream |
💛 Build succeeded, but was flakyFailed CI StepsTest Failures
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
spalger
reviewed
May 26, 2022
spalger
reviewed
May 26, 2022
| @@ -35,7 +35,10 @@ async function upToDate(settingsPath: string) { | |||
|
|
|||
| export async function setupRemoteCache(repoRootPath: string) { | |||
| // The remote cache is only for Elastic employees working locally (CI cache settings are handled elsewhere) | |||
| if (process.env.CI || !(await isElasticCommitter())) { | |||
| if ( | |||
| process.env.FORCE_BOOTSTRAP_REMOTE_CACHE !== 'true' && | |||
There was a problem hiding this comment.
Interesting side effect here gives third party devs an easy option to enable remote bazel caching without using a fake Elastic email, in case any of them are lurking about :)
spalger
approved these changes
May 26, 2022
|
This didn't make 8.2.2 removing the label. Thanks @brianseeders |
kibanamachine
pushed a commit
that referenced
this pull request
May 26, 2022
(cherry picked from commit 60226bc)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
May 26, 2022
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.
We have so many agents that run functional tests, downloading ES snapshots in all of them is a huge usage of bandwidth. We recently moved away from Cloud NAT for this reason. It was very expensive because of the bandwidth usage. It also costs a lot on the GCS bucket when we download them from other regions. This caches the snapshots in our agent images so that we don't need to download them most of the time.