cml-runner: Add an option to reuse only idle runners
See original GitHub issueToday, the --reuse
option of cml-runner
does not care if the runner is in use or not.
While it is convenient when multiple jobs can be run on the same runner, some job needs a dedicated runner to work (jobs that take the runner resources).
However, we could benefit from runner reusability for this kind of job by introducing a --reuse-idle
option to the runner. This option would reuse a runner only if it is idle (option naming to be challenged).
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Self-hosted Runners | CML
--single : Terminate runner after one workflow run. --reuse : Don't launch a new runner if an existing one has the same name...
Read more >Self-hosted workers fail immediately, get marked "offline" in ...
I used reusable only to collect the logs provided and to see whether GitHub sees the runner (it does not: it marks it...
Read more >July '21 Community Gems - Iterative.ai
Q: I'm trying to use the --reuse option of cml runner . ... You just add runners to the pool and they will...
Read more >Reuse Github Actions self hosted runner on multiple repositories
Currently, we have no methods to use the self-hosted runners across repositories, and also have no options to added self-hosted runners on ...
Read more >How do I share self hosted Windows Pipeline runner...
I don't see any option for my fork to reuse the runner that was already setup for project.git. The only option is to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
use case explanation:
cml runner --labels=xyz --single
: con: often have to wait 5min+ to provisioncml runner --labels=xyz --reuse
: con: no parallel jobs (queue waiting for one runner)cml runner --labels=xyz --reuse-idle
: this feature request: no need to wait to provision iff another job has just completed (so an idle runner is available)So true, we already face this possible race condition. I guess that it would be a minor issue to live with: the worst case would imply feeding a single runner with two tasks serially.