GitHub Community
Sharing self hosted runners across repositories #26318
-
|
Hi, I would like to set up my self hosted runner to work with not only a single repository but multiple repositories. And then I came across there is a organizational level runner solution. Can self-hosted runners be shared across organization repositories and do we have to create one per repository? It will also be useful to document how to run config.sh in non-interactive mode or automatic provisioning. Thanks Currently, I’m not setting up my repos to be part of any organization. Do I need to create an organization and transfer my account to use this feature? Also, is there another way to use a self-hosted runner for multiple repositories? Do I need to create separate directories, “actions-runner”, “actions-runner2”, and then configure separately and launch services for each repository? Please let me know what is the best practice here. Thank you, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
To use the organization level self-hosted runner , yes, you could create an organization. And then transfer your current repos in your personal account to that organization.
There is no other ways to use self-hosted runner for multiple repositories. Then you could manage repository permissions in organization settings > actions > self-hosted runner section. After you launch the runner service, all repos which you give permission could access to this runner. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you yajingzhu. I have managed to set up runners for each repo instead of making my account to organization. Hopefully there is a way to share a runner across my repos without changing my account to organization. |
Beta Was this translation helpful? Give feedback.
-
|
Hi can you please tell how to use single runner for multiple repos in an organization |
Beta Was this translation helpful? Give feedback.
-
|
no one replys that not funy guys please wee nead this feature |
Beta Was this translation helpful? Give feedback.
-
|
The somewhat sketchy but functioning workaround is to create one runner per repo in separate directories. It's clearly not optimal to have as many runners as there are repos where you could have only one runner shared accros all repositories but, while waiting for GitHub to implement such feature for "regular account/user", it's the only way that I'm aware of. It's important to notice that each runner will result in a service running on the machine and will also occupy some disk space (~ 500MB per runners after deleting the action-runner archive), so make sure your machine have enough RAM and disk space to handle them. Another important thing to notice is that, if multiple jobs are started at the same time accros multiple repos, they'll all run simultaneously since each repo has its own runner (despite them being hosted on the same machine). So it's worth noticing that, with this workaround, there's no "queue" management like it would be the case with one runner shared accros multiple repositories. Since I'm currently alone working on my repositories, I do not push nor trigger jobs to multiple repos at the same time so I'm personally not really affected by the above but it's still worth mentioning for people who could be affected by that. Anyway, as I said, that's a sketchy but functioning workaround... Clearly not optimal but it does the job while waiting for GitHub to implement a "share runner" feature accros repositories for regular users. Let's hope it happens at some point 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
I there any new feature implemented, so that can share a runner accross multiple repositories instead of creating a organization runner? |
Beta Was this translation helpful? Give feedback.
To use the organization level self-hosted runner , yes, you could create an organization. And then transfer your current repos in your personal account to that organization.
Or you could turn your personal account into an organization directly, please pay attention to the warning before you turn it.
There is the document for “Converting a user into an organization” .
There is no other ways to use self-hosted runner for multiple repositories.
If you install mu…