Mike Brouwer
Mike Brouwer

Reputation: 553

Reuse Github Actions self hosted runner on multiple repositories

I have a Self-Hosted Github Actions runner running on my server for 1 of my repositories. But now I want to use that same runner for an other repo.

Is there a way that I can reuse that same Github Actions runner for an other repo without the need of creating a new runner?

Upvotes: 36

Views: 28208

Answers (4)

Jhonny Ramirez Zeballos
Jhonny Ramirez Zeballos

Reputation: 3196

Now the organization account can create a github runner and use it in all repositories.

enter image description here

Upvotes: 5

JeroenKnoops
JeroenKnoops

Reputation: 383

We're using auto-scaled self-hosted github action runners on AWS spot instances.

We've open-sourced it: https://github.com/philips-labs/terraform-aws-github-runner

One of its creators make a blog post about it with some information about the workings: https://040code.github.io/2020/05/25/scaling-selfhosted-action-runners

Once a runner is active it can pick up multiple builds from various repositories. After a while, the idle runners are terminated. When a new workflow is triggered, a github app will create a new runner and that runner will pick up the work.

Upvotes: 5

Steven
Steven

Reputation: 1092

Update:

This is possible as of 22nd of April 2020. You can now share runners across an organization. This allows for repositories within your organization to use those runners.

https://github.blog/2020-04-22-github-actions-community-momentum-enterprise-capabilities-and-developer-improvements/#share-self-hosted-runners-across-an-organization

Old Answer:

This is not possible as of yet, according to a Github Partner:

Currently, we have no methods to use the self-hosted runners across repositories, and also have no options to added self-hosted runners on Organization level.

Source: https://github.community/t5/GitHub-Actions/Can-one-Github-Actions-self-hosted-runner-work-for-multiple/td-p/41465

Upvotes: 21

Mike Brouwer
Mike Brouwer

Reputation: 553

For those that want to know what I did to fix this problem. I installed multiple GitHub runners on my server with different names. Not the best solution, but the only thing thats possible now without a dirty workaround...

Upvotes: 9

Related Questions