siraf
02/17/2023, 1:33 PMruns-on
.
Tried putting it in each place of the yml, with and without steps
, env
, with
etc. and each time the Github Action fails.
Did anyone else use his own runner, if yes, please write where did you put the runs-on
line, thanks.
name: KMM Bridge/iOS Publish
on:
workflow_dispatch:
jobs:
call-kmmbridge-publish:
uses: touchlab/KMMBridgeGithubWorkflow/.github/workflows/faktorybuildbranches.yml@v0.6
secrets:
PODSPEC_SSH_KEY: ${{ secrets.PODSPEC_SSH_KEY }}
This is one of the ways I tried (adding runs-on right below the job name):
jobs:
call-kmmbridge-publish:
runs-on: self-hosted
steps:
- uses: touchlab/KMMBridgeGithubWorkflow/.github/workflows/faktorybuildbranches.yml@v0.6
with:
PODSPEC_SSH_KEY: ${{ secrets.PODSPEC_SSH_KEY }}
Jacob Ras
01/02/2024, 10:31 AMruns-on
because this is a reusable workflow, which set the runners itself in its steps. But, Touchlab made a property to set the runner and it passes it on to the actual steps (see runsOn
in https://github.com/touchlab/KMMBridgeGithubWorkflow/blob/main/.github/workflows/faktorybuildautoversion.yml). It's used like this:
jobs:
call-kmmbridge-publish:
with:
runsOn: your-runner-name
Jacob Ras
01/02/2024, 10:33 AMCalled workflows cannot be queued onto self-hosted runners across organizations/enterprises