[JIRA] (JENKINS-38715) Container instance cannot be empty error

2016-11-11 Thread nando.s...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nando Sola edited a comment on  JENKINS-38715  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Container instance cannot be empty error   
 

  
 
 
 
 

 
 I'm getting the same error when the desired capacity of the autoscaling group is set to zero. Our ideal use case would be that the plugin launched a new  EC2  cluster  instance before deploying the task. This is useful in terms of not having an idle  EC2  instace waiting for tasks.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38715) Container instance cannot be empty error

2016-11-11 Thread nando.s...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nando Sola commented on  JENKINS-38715  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Container instance cannot be empty error   
 

  
 
 
 
 

 
 I'm getting the same error when the desired capacity of the autoscaling group is set to zero. Our ideal use case would be that the plugin launched a new EC2 instance before deploying the task. This is useful in terms of not having an idle instace waiting for tasks.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-38715) Container instance cannot be empty error

2016-10-04 Thread jgang...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jae Gangemi created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38715  
 
 
  Container instance cannot be empty error   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jan Roehrich  
 
 
Components: 
 amazon-ecs-plugin  
 
 
Created: 
 2016/Oct/04 8:21 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jae Gangemi  
 

  
 
 
 
 

 
 i am getting the following error when trying to launch a build into ecs: 

 

com.amazonaws.services.ecs.model.InvalidParameterException: Container instance cannot be empty. (Service: AmazonECS; Status Code: 400; Error Code: InvalidParameterException; Request ID: 0c26d03e-8a6c-11e6-be2f-71463a1d5d9f)
	at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1307)
	at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:894)
	at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:597)
	at com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.java:363)
	at com.amazonaws.http.AmazonHttpClient.executeWithTimer(AmazonHttpClient.java:329)
	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:308)
	at com.amazonaws.services.ecs.AmazonECSClient.invoke(AmazonECSClient.java:)
	at com.amazonaws.services.ecs.AmazonECSClient.describeContainerInstances(AmazonECSClient.java:876)
	at com.cloudbees.jenkins.plugins.amazonecs.ECSService.waitForSufficientClusterResources(ECSService.java:180)
	at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:255)
	at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:237)
	at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at