For more information, see " Moving a runner to a group."įor information on how to route jobs to runners in a specific group, see " Choosing the runner for a job." Managing access to your runners You can move runners from one runner group to another. Runners can only be in one group at a time. When new runners are created, they are automatically assigned to the default group unless otherwise specified. Optionally, you can assign additional granular repository access policies to the runner group. When you grant access to a runner group, you can see the runner group listed in the organization's runner settings. Organization owners can configure access policies that control which repositories in an organization have access to the runner group. You can then decide which organizations or repositories are permitted to run jobs on those sets of machines. Runner groups are used to collect sets of runners and create a security boundary around them. To control access to runners at the organization level, organizations using the GitHub Team plan can use runner groups. Note: The information and instructions in this article only apply to larger runners with Linux and Windows operating systems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |