Ability to restrict runner usage
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.
Support auto-scaling for self-hosted runners
Automatic scaling to handle changing workloads - AWS ASGs, Kubernetes, etc.
Docker Based Runner for Behind-The-Firewall use
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
Display steps not executed when a job fails
We can have lots of steps in a job and and when the job 9 of 10, by example, fails it is hard to figure it out that it missed another step.
Add Support for s390x and ppc64le
Providing support for s390x(Mainframe) and ppc64le(PowerPC) would allow the community to build on those architectures. Many open source communities build there software for a wide range of architectures. Having a one stop shop for a CI/CD platform that can build all the architectures need would be huge. Currently, many open source projects need to split their builds/tests across multiple CI/CD system making it hard to manage. In addition to the open source community, many big companies rely on s390x and ppc64le architectures for their core systems. i.e Big Banks, Airlines, Credit Cards, etc If CircleCI add support for these architectures it would allow them to approach new customers and communities.
Runner UI - Easier to scroll through list of Runners
For teams using a number of runners, the UI list can be tedious to scroll through. The ask is to figure out how to make the Runner UI easier to scroll through.
better Rust support
I need image with Rust and trunk installed. Otherwise I need to create my own image every build - it is kind of annoying
Support 32-bit ARM on self-hosted runners
There are plenty of low powered IoT devices that are still running 32-bit ARM processors. Ability to consolidate CI testing into CircleCI would be extremely valuable.
Support emitting metrics to data solutions for runners
Specifically tools like statsd, Prometheus, etc.