-
Bug
-
Resolution: Won't Fix
-
Major
-
None
When attempting to allocate an agent using:
agent { label '' }
It will grab the first available agent. This appears to be equivalent to `agent any`. I would expect this to fail instead of silently grabbing an agent.
This is generally easy to work around at a stage agent assignment (can precondition fail using a earlier stage), but can't be caught at the pipeline level easily. This can be a serious problem depending on your agent infrastructure and which job is running.