Hello,
Currently, when we add a runner in Release, it is configured as an instance runner and receives a default capability (such as remote).
We would like to add a second runner and remove this default capability.
The reason is that we do not want standard tasks to run on the new runner. It should only be selected when a specific capability is explicitly assigned.
Regards
Limeng
by: Limeng L. | about a day ago | Administration
Comments
Thank you for sharing the idea. A few possible approaches that we would like to validate for your use case:
- Allow removing the default remote capability from a runner, so it only picks up tasks that explicitly request it.
- Route tasks to runners based on the connection used (for example, a GCP connection goes to the GCP runner, an on-prem connection goes to the on-prem runner).
- Use custom capabilities as an interim option, with a script to update tasks in bulk.
The Field team will reach out to discuss which one fits the use case best.