Previously, you could assign Plans to Queues. This gave you the ability to control exactly what Plans would run on a given Queue.

Now, each Plan has requirements, that may be met by any number of Agents. You cannot forbid Plans from running on an Agent: if the Agent meets the requirements of a Plan, it will greedy build any of those Plans.

Desired It would be good to be able to configure an Agent to only run a given set of Plans. For example, you might want have an Agent that has the same capabilities as any other Agent, but is always available to do a particular build as soon as a commit occurs to a given codebase – it is not acceptable for that build to wait on the next available matching Agent.

Current workaround Create n-squared properties on each Plan and Agent, excluding all-but-one Plan from running on a given Agent.

Proposal: Agent Prerequisites

Currently Plans state requirements that are satisfied by Agents.

We could add a reverse of that relationship:

• Agents can state Prerequisites that are satisfied by Plans

For example, an Agent could have a Prerequisite "clover-optimized-build-only". And only Plans that satisfy that Prerequisite will run on that agent.

(NB: this should apply to all agent types, remote, local, etc.)