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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.