Pipeline-wise agent queue selection

Features Requests
1

Hi team!

Do we have a way to specify a queue to use at pipeline level, and all the steps will use this queue instead of default? Our use case is we have recently migrated to only allow a special agent(infra) to access some of our AWS accounts, and it is really tedious to redefine the queue for every step.

If not, can I suggest that we read the pipeline agent from an environment variable, so we can either define that at the top level, or we can pass it in from a parent pipeline?

Thanks!

Regards,
Kai

2

We use named anchors to DRY up our YAML; it works, but only within one pipeline at a time. If there’re more than one pipeline in the same repo, those individually each contain the same boilerplate.