Runner

In cases where you may need to debug a build, it would be great to have access to debug with SSH on container runner.

It would be helpful to add a label to the pod that is running the task with the real job-name to easily reference which pod is running which task. These labels can then show up in our observability platform and we can easily aggregate across the same job type. Right now we can only do it by resource class

I've been told that the reason why the container-agent chart need to deploy a ClusterRole is to automatically detect the CPU architecture of the node. Since the ClusterRole applies to the entire k8s cluster, there's some policy limitation in my org which makes deploying a ClusterRole complicated. It would be great if the chart allows specifying CPU architecture via a field in values.yaml so that we don't have to deploy the ClusterRole.

As a CircleCI SaaS user with Behind-the-firewall resources (artifacts, databases, services) I want to easily run select jobs on my internal network rather than CircleCI’s network. Unlike current Machine Runner: I should not need to define or publish custom images I don’t or won’t use for my other jobs in cloud. I should not need to manage dependencies or libraries on said runner (instead provided by my docker images). I should not need to recycle physical or virtual servers to get a clean build environment (instead provided via each docker container – as with cloud). In short, my existing cloud jobs should be easily ported to run on my docker runner in my internal network

To reach parity with existing non-runner jobs, the add_ssh_key ( https://circleci.com/docs/2.0/configuration-reference/#add_ssh_keys ) step should be supported. This will allow use of additional configured keys for pushing tags and generated-commits. The key should be added in a way that remains scoped to the runner job - and not globally on the hosting machine.

Currently self-hosted runners only available for Ubuntu arm/x86 and macOS x86. Would like self-hosted runners on CentOS

Although the parallelism feature does work on self-hosted runners, the downloading of previous test results is not currently supported - which means that the intelligent test splitting feature does not work. In addition, the standard circleci tests split invocation of test splitting requires the circleci CLI or the circleci-agent binary to be available.

Right now, the process of filtering for jobs requesting runners is extremely painful: at least 3-4 API calls to fetch the pipelines, then the workflow(s) in the pipeline, then the job(s) in the workflow, and then finally a manual scan for a specific runner resource class. I should be able to make a single API call and get all jobs that are requesting a runner resource (or any resource, really)

At the moment when a new agent version is released, there isn't much information around what has changed. In addition, there isn't a way to get notified a new version was released. Similar to the server product: https://circleci.com/server/changelog/ Provide a change log for the Runner product that gets updated when a new agent version is released.

Currently self-hosted runners only available for Ubuntu arm/x86 and macOS x86. Would like self-hosted runners on Windows