We’re testing devices and have one agent per channel in our test environment. When multiple builds are generated for a particular agent population and pipeline, it looks like that work isn’t getting evenly distributed across the eligible agents. For example, you have 10 agents with a foo=true metadata tag and continuously ensure that there are always at least 3 build requests targeted at those agents. I was sort of expecting the builds to be evenly distributed (over time) across all 10 of agents, but the actual result is that certain agents tend to get the work.
Am I completely off base here? If not, is there some sort of workaround? I’m kind of thinking I’ll need to do something like make an API call in one pipeline to identify the agent population and then use that info to schedule builds for each matching agent in a separate pipeline (after adding something to ensure that I can target each of those requests to a specific hostname.)