Problem

On the server capabilities the All Remote Agents doesn't work well when you have remote agents on different types of systems that use different file systems, mainly Windows vs. Unix. So when you have something like Maven it could be installed in one location on Unix Remote Agents and in a different location on Windows Remote Agents. Although you can override this at the remote agent level either manually or through a bamboo-capabilities.properties file, being able to define remote agent types would allow them to be defined for All <Type> Remote Agents, for example All Windows remote agents, All Linux remote Agents.

Suggestion

Add the ability to specify a Remote Agent Type, so we can say All Unix Remote Agents have Maven 3.3.9 at this location and All Windows remote agents have Maven 3.3.9 at this location. That way we could still define a shared component for remote agents without having to override it at the agent level for all agents that don't match the default.

The solution could use an Agent Type field, which would allow users to define Agent Types, then allow for defining shared capabilities by type or allow the path to be set by type in the definition of a capability. Name: Maven 3.3.9 Path: Agent Type: windows, path: c:\whatever. Agent Type: Linux, path /production/whatever.

Then when creating a new remote agent if the type could be specified it would automatically inherit the correct shared capabilities without having to override them at the agent level.