cache: propagate github instance slug - #27
Closed
max-blacksmith wants to merge 1 commit into
Closed
max-blacksmith wants to merge 1 commit into
max-blacksmith wants to merge 1 commit into
Conversation
Author
|
This information shouldn't be passed like this. |
This file contains hidden or 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
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.
Cache requests need the GitHub instance identity so matching owner/repo names on different instances cannot share entries.
Read
BLACKSMITH_INSTANCE_SLUGfrom the runner environment and sendX-Blacksmith-Instance-Slugon restore, reserve, and commit requests. Missing values default togithubfor existing dotcom runners.Targets
useFetchAsHTTPClient, the branch with the cache package used by the actions. Two header propagation tests passed on Testbox; Prettier passed.Deploy the backend and agents first. After merging, publish the cache package, update pinned dependencies in the cache/setup actions, and rebuild their bundles before enabling non-dotcom caching.
Companion PRs: backend, agent.