Cache paths env var #2720
Merged
Cache paths env var #2720
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
DrJosh9000
approved these changes
Apr 9, 2024
matthewborden
approved these changes
Apr 9, 2024
This was referenced Apr 9, 2024
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.
Description
Buildkite's upcoming hosted compute product will include a feature to mount cache volumes when instructed to do so by the buildkite backend. Though the mounting itself happens outside of the agent, the agent needs to tell the mounter where to mount the cache volumes.
This PR adds the ability for the agent to consume the cache paths from the accept job response, and pipes those paths through to an envar
BUILDKITE_AGENT_CACHE_PATHS.Context
COMP-321
Testing
go test ./...). Buildkite employees may check this if the pipeline has run automatically.go fmt ./...)