When adding a new self-hosted runner, IDs and credentials are created that are specific for a single agent (e.g. the RUNNER_UUID parameter).
This makes it hard to auto-scale runners. If the parameters would be reusable it would be easier to automatically scale up on a high demand of runners and scale down if no agent is needed at the moment.
Do you have any suggestions on that topic?
Please support this ticket https://jira.atlassian.com/browse/BCLOUD-21304 as it should help address your question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.