Unable to prevent certain jobs from using registered org level runners for other jobs

[NorseGaud]

Select Topic Area

Question

Body

I'm building a golang app that listens for webhook events for jobs and, if certain labels are found, creates a macOS VM and registers it to the org level. So far it works.

However, because multiple jobs can be created with the same labels, suddenly we get one job picking up the VM intended for another.

I know I can add a label specific to the workflow with contextual information, but I've had customers beta testing this and saying that they don't want their users accidentally forgetting to add it to the labels or messing it up; basically that they want to keep the runs-on as light as possible.

Therefore, I'd like to try and find a way to add a label when I go to register the runner that is already enabled in the job without me having to define it under runs-on. Does this exist? I imagine it would look like workflowID or something and I would just register with workflowID:${wID}.

I've got the following:

name: 't1-with-tag-1-matrix-nodes-2'
on:
  workflow_dispatch:
jobs:
  t1-with-tag-1-matrix-nodes-2:
    strategy:
      matrix:
        nodes: ["1", "2"]
    runs-on: [ 
      "self-hosted", 
      "anka", 
      "anka-template:d792c6f6-198c-470f-9526-9c998efe7ab4", 
      "anka-template-tag:vanilla+port-forward-22+brew-git",
    ]
    steps:
 . . .

I hope there is something! Thanks!

[NorseGaud]

It looks like I need some sort of default labels added that are specific to the runID and JobID. Seems like OSX and Arm64 are there... --no-default-labels Disables adding the default labels: 'self-hosted,OSX,Arm64'

[khvci]

[NorseGaud]

Hey @khvci , it looks like maybe the formatting is off a bit in your reply. Thanks for the follow up regardless!

For now I've made a note that if customers are using the template across jobs that they need to use something like

    strategy:
      matrix:
        node: [1, 2]

      runs-on: [
        "anka-template:ccd13ed8-6704-47a9-80ad-7ed64349c6d9",
        "unique-id:${{ github.run_id }}-${{ matrix.node }}"
      ]

I've also used --no-default-labels so that anka and self-hosted aren't needed anymore.

I am curious about Register the VM with Conditional Logic:. What would this script do? I sounds, and this is based on limited understanding of the scripts you are talking about, that it would cause the job that tries to use the VM to fail... Can you clarify just a tiny bit more about this? Here is our current registration script (it's important to note that this is an ephemeral setup and we won't have long-running VMs/runners registered):

#!/usr/bin/env bash
set -exo pipefail
[ -z "$1" ] && (echo "Error: Runner name argument is missing." && exit 1)
[ -z "$2" ] && (echo "Error: Token argument is missing." && exit 1)
[ -z "$3" ] && (echo "Error: URL argument is missing." && exit 1)
[ -z "$4" ] && (echo "Error: Labels argument is missing." && exit 1)
RUNNER_HOME="${RUNNER_HOME:-"$HOME/actions-runner"}"
if [[ -n "${5}" ]]; then
  RUNNER_GROUP_FLAG="--runnergroup ${5}"
fi
mkdir -p "${RUNNER_HOME}"
cd "${RUNNER_HOME}"
eval ./config.sh --name "${1}" \
  --token "${2}" \
  --url "${3}" \
  --no-default-labels --labels "${4}" \
  --disableupdate \
  --unattended \
  --ephemeral \
  ${RUNNER_GROUP_FLAG}
echo "runner successfully configured"

The more I think about it, the more this seems like it is a feature request to be able to set, given the presence of a runs-on label, default labels it looks for matching on registered runners. Let's say that anka exists. I should be able to tell it to then look for workflowID and maybe also runID which I can have the golang code pass into the registration bash script. What do you think?

[NorseGaud]

Bump

[NorseGaud]

bump