CODEWITHSUNDEEP
githubgithub-actions
Pierre
Pierre

Reputation: 2902

Github Actions: No runner matching the specified labels was found: ubuntu-latest

My organisation uses "GitHub Enterprise Server 3.0.1" (in case this has any impact).

I created a .github/workflows/scala.yml file in my project. The Github Action gets triggered just fine but it dies with this error:

"No runner matching the specified labels was found: ubuntu-latest."

I tried to change it to ubuntu-20.04 and now I get:

"No runner matching the specified labels was found: ubuntu-20.04."

Same result, no matter if I trigger the action manually or check-in/push a change to my Development branch: the action triggers but fails with the above errors (and I get an email from GitHub telling me my build-job failed). I have a feeling this might be a YAML parsing issue. I confirm that there are no spaces nor weird/invisible characters after the "ubuntu-latest" string/line (I checked in my Hex editor). Any ideas?

Here is my scala.yml:

name: Scala CI

on:
  workflow_dispatch:
  push:
    branches:
    - Development
  pull_request:
    branches:
    - Development

jobs:
  build-job:
    runs-on: ubuntu-20.04

    steps:
    - uses: actions/checkout@v2
    - name: Set up JDK 1.8
      uses: actions/setup-java@v1
      with:
        java-version: 1.8
    - name: Run tests
      run: sbt test

Upvotes: 5

Views: 6245

Answers (1)

Pierre
Pierre

Reputation: 2902

This page holds the answer: Github Enterprise (GHES) doesn't support GitHub-hosted runners...

https://docs.github.com/en/[email protected]/admin/github-actions

"GitHub-hosted runners are not currently supported on GitHub Enterprise Server. You can see more information about planned future support on the GitHub public roadmap."

The roadmap for this feature in GHES is here: https://github.com/github/roadmap/issues/72

And this feature, on the roadmap, has been moved from "Q2 2021" to " the future":

"github-product-roadmap moved this from Q2 2021 – Apr-Jun to Future in GitHub public roadmap on Apr 7"

So, it looks like I need to runs this as:

runs-on: self-hosted

Upvotes: 4

Related Questions