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
Hi @spasam, currently they are per repository. We’ll be working on enabling them for organizations in the future.
For an example on how to do it hands-off (noninteractive):
This is something that we’d very much like as well, likely can’t use github actions + self-hosted runner until then.
Mainly trying to get cached docker builds to run subsequent steps without having to rebuild / re-pull images, which a self-hosted runner would help us do given the way that github actions runs parallel jobs across multiple machines
Any progress on this? We just moved across fom GitLab and found ourselves in an impossible situation to share self-hosted runners. This has a high impact on our work and if not resolved soon will have to roll-back.
Agreed that this limitation makes self-hosted runners basically unusable for our needs.
Any ETA on this being changed?
It can be done, add multiple runner services on your machine for now.
It’s actively under development. I don’t have a date yet that I can share. Getting it released as soon as we can.
Sorry to bring this up again, but do you now have an ETA given one month has passed since your latest feedback?
It’s not a very big issue to start runner repositories separately, but I don’t think github will be aware of runner idle status across repositories. This means separate repositories can start builds on the same machine, which might cause high resource overload for the same machine.
Is there any workaounds available for the problem I mentioned?
Organization level runners are now available.