-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
jenkins 2.176.2, EC2-fleet-jenkins-plugin 1.10.0
If we have 4 EC2 spot fleet clouds configured to spin a maximum of 20 instances based on the agent label specified, if a jenkins job with no agent specified is executed, the build stays in the queue searching for agents and this is triggering all the 20 possible instances. Expected result would be to spin the instance only if the label assigned to the cloud is matched with the label specified in the Job