[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 Lab

2019-11-14 Thread baisani.sivanaray...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 sivanarayana baisani closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 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   
 

  
 
 
 
 

 
Change By: 
 sivanarayana baisani  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201131.1565037052000.1481.1573770120420%40Atlassian.JIRA.

[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 Lab

2019-08-05 Thread baisani.sivanaray...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 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