-
|
Hi! I have something of an edge case question I was hoping someone can help with. Our Github Enterprise administrators let us register self-hosted runners for individual repositories but not for a whole organization; our organization is fairly flat. I thought I would just register runner sets for each repo but we are using reusable workflows and it looks like you can't pass in a value for runs-on from a calling repo into the called workflow. This led me to believe that maybe I could deploy runner sets with unique names but a shared custom label that I could register and reference in the reusable workflow. However, the chart for installing more runner sets doesn't seem to have this and the AutoscalingRunnerSet type doesn't seem to have a place where I can add extra labels that a workflow could select on. Does anyone have thoughts on how I can use the 'new' system for runners in this situation? I'd rather not repeat the same workflow in every repo that needs it. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Found the answer. It looks like I found old information that runs-on can't be overridden. Enterprise 3.10 documentation says you can change it based on an input: https://docs.github.com/en/[email protected]/actions/using-jobs/choosing-the-runner-for-a-job I've tested and confirmed it. |
Beta Was this translation helpful? Give feedback.
Found the answer. It looks like I found old information that runs-on can't be overridden. Enterprise 3.10 documentation says you can change it based on an input: https://docs.github.com/en/[email protected]/actions/using-jobs/choosing-the-runner-for-a-job I've tested and confirmed it.