Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Compatibility with GitHub-hosted runners #52

Closed
cheahjs opened this issue Aug 14, 2024 · 2 comments
Closed

Compatibility with GitHub-hosted runners #52

cheahjs opened this issue Aug 14, 2024 · 2 comments

Comments

@cheahjs
Copy link

cheahjs commented Aug 14, 2024

I was wondering what is the story like with GitHub-hosted runners. The current instructions require patching the runner, but this is done on disk prior to launch and is only feasible for self-hosted runners, but with GitHub-hosted runners, any steps that are run inside of a workflow are with an already running runner?

This might require patching the runner in memory - has anyone attempted this before?
@LouisHaftmann
Copy link
Collaborator

LouisHaftmann commented Aug 14, 2024 •
edited
Loading

It is probably not possible to use this cache server with Github hosted runners unless Github finally allows overwriting ACTIONS_CACHE_URL at runtime

@LouisHaftmann
Copy link
Collaborator

Closing this for now (more info here actions/toolkit#1695)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cheahjs @LouisHaftmann