-
Notifications
You must be signed in to change notification settings - Fork 964
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
self-hosted organization runner does not pick up jobs #831
Comments
Just to add: I am running into the same issue with runners on Windows |
I changed my account to an organisation so that I do not have to configure the self-hosted runners for each repository individually. At the beginning I also had the error message mentioned above. Are you sure it is a private repository? The self-hosted runners are only allowed for private repositories for security reasons. The self-hosted runners are only displayed for private repositories. Public repository: I think the error message is a bit misleading. Instead of stating that no self-hosted runner was found with the label in question, it should be pointed out that self-hosted runners are only allowed for private repositories. |
@dhoppe why do you think self-hosted renners are only allowed from private repos? Where is it stated? |
Just take a look at my first screenshot.
You could create a new group which also allows public repositories, but this requires a GitHub Enterprise account. |
@dhoppe Thank you, that worked! I even was able to modify the I think this issue can be closed then. |
Just got here after scratching my head on what was happening. Would be good to improve the error message in the logs to state this more clearly! So a job that would be eligible on that runner seems to trigger and then fails with this message hidden deep in the logs as a hint? |
I have this same problem. I can get my self-hosted runners will work just fine on public repos using the fully permissive setup (Selecting "all repositories" and "all workflows"), my self-hosted runners do not deploy if I try restricting access to some repositories or workflows. I've created a "runner group" with access to "selected public repos", and I can see the runner listed in the settings->actions->runner page of the public repo (screenshot below). But when I set runs-on: self-hosted it just stalls out "waiting for a runner to pick up this job". What did I miss? I also list Only when using private repos, or otherwise, if I allowing runs on all public repos will my self-hosted runner pick up the jobs. What am I missing here? |
Describe the bug
The organization-wide self-hosted runner does not pick up jobs. Note, that repository self-hosted runners work ok.
To Reproduce
Steps to reproduce the behavior:
runs-on: [self-hosted]
are not picked up, constantly showing "Starting your workflow run...". After some timeout those jobs fail with "This check failed".Expected behavior
The jobs which have
runs-on: [self-hosted]
are picked up by the self-hosted runner.Note, if on step 1 the runner is registered to a repository instead of organization, then it works.
Runner Version and Platform
Runner version:
2.274.2
Ubuntu-18.04
What's not working?
After workflow fails there are messages "No runner matching the specified labels was found: self-hosted." on the "This run" page.
Job Log Output
N/A
Runner and Worker's Diagnostic Logs
The text was updated successfully, but these errors were encountered: