[JIRA] (JENKINS-58819) When a Jenkins job with no agent or wrong agent is executed, the EC2 fleet plugin is spinning up all the possible instances in all the clouds configured with different Agent Labels

2 views

Skip to first unread message

baisani.sivanarayana@gmail.com (JIRA)

unread,

Aug 5, 2019, 4:31:04 PM8/5/19

to jenkinsc...@googlegroups.com

sivanarayana baisani created an issue

Jenkins /

JENKINS-58819

When a Jenkins job with no agent or wrong agent is executed, the EC2 fleet plugin is spinning up all the possible instances in all the clouds configured with different Agent Labels

Issue Type:	Bug
Assignee:	Chad Schmutzer
Components:	ec2-fleet-plugin
Created:	2019-08-05 20:30
Environment:	jenkins 2.176.2, EC2-fleet-jenkins-plugin 1.10.0
Labels:	plugin
Priority:	Major
Reporter:	sivanarayana baisani

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