Runner

Would like the ability to restrict who can use certain runners in an org, similar to how we can restrict who has access to contexts.

It would be great if there was a way to limit the concurrency down to a specific runner resource class so that queued builds to not affect other resource classes.

Currently, the %s wildcard is not supported in Runner 3.0 working directories and will be interpreted as a literal value. > For Machine Runner 3.0, the %s substitution feature is not supported. The %s value in the working directory path would be interpreted as a literal value. https://circleci.com/docs/machine-runner-3-configuration-reference/#runner-working-directory This feature request is to introduce the %s wildcard for use within the runner.working_directory parameter in a runner's configuration file.

Would be nice to specify multiple executor/resource types in a ranked preference order. I could have multiple self-hosted runner resource classes I've created, and if one has no nodes available, CircleCI moves down the list to the next resource class. It would be nice if the list could also include cloud executor types - if none of my self-hosted runner classes have nodes available, then I default to using a CircleCI-hosted node.

Given a resource class, it would be great to have an API to see what job(s) are queued on said runner. This would enable teams to see what/where their runners are being used and if something is "stuck".

It would be great if the Runner team could provide a CircleCI solution within Container Runner that is similar to Buildah/Kaniko to allow the usage of Docker in Docker.

Specifically tools like statsd, Prometheus, etc.

In some cases, it may be good to surface Container Runner metrics to Prometheus. Such as Task count, Task limit, error logs, etc.

Currently, if a runner is inactive, there is no way to delete the runner without deleting the resource class. The inactive runner will fall off inventory after 12 hours of inactivity. > https://circleci.com/docs/runner-faqs/#how-long-do-inactive-self-hosted-runners-persist-in-the-self-hosted-runner-inventory-page This feature request is to enable the ability to delete a runner within a resource class without waiting the 12 hours or deleting the entire resource class

Similar to running jobs using CircleCI's machines, it would be ideal to have the same for Runners using our own architecture. The CPU and RAM columns are blank for some jobs in our insights dashboard, particularly the self-hosted runner jobs.