Question

Your enterprise has a self-hosted runner group named 'gpu-builders' created at the enterprise level, currently granted to two organizations. A third organization, 'ml-research', is onboarded and needs to run jobs on these runners. After the enterprise owner adds 'ml-research' to the runner group's organization access list, the org admin reports that no repositories in 'ml-research' can queue jobs to 'gpu-builders'. What additional step is required?

Accepted Answer

The 'ml-research' org admin must configure repository access for the runner group within the organization's settings, since org-level repo access is managed separately from enterprise-level org access.

Answer

The enterprise owner must add each repository in 'ml-research' individually to the enterprise runner group's access list.

Answer

The runners must be re-registered with a new registration token scoped to the 'ml-research' organization.

Answer

The enterprise owner must change the runner group visibility to 'All organizations' because selected-org groups cannot be shared beyond two organizations.