[JIRA] (JENKINS-29851) global instance cap not respected for spot instances
Title: Message Title A B commented on JENKINS-29851 Re: global instance cap not respected for spot instances Our workaround is to manually launch instances before sending the jobs to Jenkins. This is a luxury we have, based on our configuration, that others may not have. But I wanted to share it anyway. If the instances are already idle (or in use) then the instance cap is respected and additional slaves are not initiated. It suggests to me that, when inspecting the instance cap, instances that are currently booting up are being ignored. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50931) EC2 Instance cap is not respected
Title: Message Title A B commented on JENKINS-50931 Re: EC2 Instance cap is not respected An update - the problem is definitely getting worse. With an instance cap of 1, I am routinely getting 10 or more slaves starting up. Only thing that has changed is AWS (I haven't changed the Jenkins configuration at all). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-29851) global instance cap not respected for spot instances
Title: Message Title A B reopened an issue Our instance cap is set to 1, but seems to be completely ignored. Not uncommon for 10 instances to be launched simultaneously. Is there anything required in our EC2 environment / AMI in order for the instance cap to be respected? Jenkins / JENKINS-29851 global instance cap not respected for spot instances Change By: A B Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50931) EC2 Instance cap is not respected
Title: Message Title A B created an issue Jenkins / JENKINS-50931 EC2 Instance cap is not respected Issue Type: Bug Assignee: Francis Upton Attachments: 1 - Configure EC2 plugin.png, 2 - Multiple instances are launched.png, 3 - Software versions.png Components: ec2-plugin Created: 2018-04-23 04:06 Environment: Jenkins version: 2.107.1 ec2-plugin version: 1.39 Java version: 8u151 OS: Linux (4.4.0-1052-aws) Labels: ec2 ec2-plugin aws configuration Priority: Major Reporter: A B In Manage Jenkins -> Configure System -> Cloud -> Advanced, I set "Instance Cap" to 5 I push changes to many branches (more than 5) In the sidebar, I see that more than 5 instances have been created. I expected that a maximum of 5 instances would be created. I am using EC2 spot instances in the ap-southeast-2 region. I have only one 'cloud' set up, and all the instances are building (different branches of) the same job. Please let me know if any other information would be helpful. (I see that this bug has been reported previously, but closed. Is this a regression? Am I doing something wrong?)
