We’re just starting to use GH Actions to enable some continuous deployment to an AWS ECS Fargate cluster. We deploy a node container whose build time is eating into our minutes, so we’ve deploy self-hosted runners to give a bit more horse power to the build and cuts it in about a third. (as a quick aside–I have to to commend the GH folks here setting up the self-hosted runners we super straightforward and worked basically the first time. kudos!!!)
It seems with the default config outlined here it sets up the runner to run a single job at a time. I was wondering if there is a configuration out there that would allow the runner service to take more then one job off the queue at once and thus get a bit of easy-to-stand-up virtical scaling, and if not is this or something like a configuration that is more condusive to AWS AutoScalingGroups where the instances are more ephemeral be something on the roadmap?