Recently I find myself wanting to test my pipelines on different agents because I’m trying to replace some older agents. Currently the only way to do this is to manually modify the code where my pipelines are defined and change the targeting queue tag values.
But I think the ideal solution would be to have this supported in Buildkite somehow.
Here’s my ideal scenario:
- I trigger a build for a pipeline either through the UI or via API and specify a custom queue override (eg. with an env var like
BUILDKITE_AGENT_META_DATA_QUEUE=something_new- but the specific env var or mechanism can be different).
- Buildkite recognizes this and overrides all agent targeting for all a) jobs in the build (including dynamically added ones) and b) all triggered pipelines from the build, regardless of what the targeting parameters are in each pipeline’s YAML/uploaded code.
Would this be feasible to have as a feature in Buildkite?