This repository has been archived by the owner on Oct 28, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
ci: stash/unstash steps with Google Cloud Storage #531
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
v1v
changed the title
ci: support stash/unstash with GCS
WIP ci: support stash/unstash with GCS
May 13, 2020
v1v
commented
May 13, 2020
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
|
… into feature/stashv2 * 'feature/stashv2' of github.com:v1v/apm-pipeline-library: Write credentials for opbot (#529) Add flake detector to pipeline (#530)
v1v
commented
May 14, 2020
@@ -93,7 +93,6 @@ unclassified: | |||
filterSettings: | |||
includeFilter: false | |||
selectors: | |||
- wildcard: "*.*" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fix an issue
v1v
changed the title
WIP ci: support stash/unstash with GCS
ci: support stash/unstash with GCS
May 14, 2020
kuisathaverat
approved these changes
May 14, 2020
cachedout
reviewed
May 14, 2020
mdelapenya
approved these changes
May 14, 2020
cachedout
approved these changes
May 14, 2020
If configuring a retention policy and possibly other parameters on the Google side are necessary, should that process be documented in this PR? |
* upstream/master: Fix missing Docker login (#533)
@cachedout good point, I just pushed 84734aa#diff-64f8c926883b22c4ce3299295ee2235fR32 |
cachedout
reviewed
May 14, 2020
v1v
commented
May 14, 2020
v1v
commented
May 14, 2020
Co-authored-by: cachedout <mike.place@elastic.co>
v1v
changed the title
ci: support stash/unstash with GCS
ci: stash/unstash steps with Google Cloud Storage
May 14, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What does this PR do?
Why is it important?
Will allow to run the pipelines faster.
Related issues
Caused by elastic/beats#18473
Tasks
move
/mv
commandsTests
Real scenarios
build
ITs