Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can this work with Runner group at enterprise level #350

Open
Deepak1100 opened this issue Oct 28, 2021 · 3 comments
Open

Can this work with Runner group at enterprise level #350

Deepak1100 opened this issue Oct 28, 2021 · 3 comments
Labels
question Further information is requested

Comments

@Deepak1100
Copy link

i have installed the operator and used GitHub App to authenticate. and it worked fine when it comes to runner group at org level.
But does it support runner groups at the enterprise level?

Self-hosted runner groups are used to control access to self-hosted runners at the organization and enterprise level

Cause when I tried it's giving me 404.

Usecase: wanted to manage the runner group across orgs.

@davidkarlsen
Copy link
Collaborator

yes, just pass:

- name: ACTIONS_RUNNER_INPUT_RUNNERGROUP
  value: "thegroupname"

to the runner env.

note that the group needs to exist (you can create it through the UI).

@davidkarlsen davidkarlsen added the question Further information is requested label Oct 28, 2021
@Deepak1100
Copy link
Author

Yes, i already did that but it was giving 404. again this is an enterprise runner group that can be used by multiple organisations at the same time

@Deepak1100
Copy link
Author

Deepak1100 commented Oct 28, 2021

https://docs.github.com/en/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups

GitHub Docs
You can use policies to limit access to self-hosted runners that have been added to an organization or enterprise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants