[
https://issues.jenkins-ci.org/browse/JENKINS-7883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159143#comment-159143
]
francis Upton commented on JENKINS-7883:
----------------------------------------
Will fix this to count only the running or pending instances as active against
the count, all other will be ignored.
It was deliberate to use the EC2 instance counts to manage this, and I think
it's a good idea to continue that way (as opposed to having a separate Jenkins
count), so that won't be changed.
> Stopped (as opposed to terminated) slaves are counted against the active
> instance count for the purpose of launching; can prevent launching of
> instances
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JENKINS-7883
> URL: https://issues.jenkins-ci.org/browse/JENKINS-7883
> Project: Jenkins
> Issue Type: Bug
> Components: ec2
> Affects Versions: current
> Environment: ubuntu amd64 e.g. alestic ami-da0cf8b3
> ec2 plugin v 1.9
> Reporter: truher
> Assignee: Kohsuke Kawaguchi
> Priority: Blocker
>
> i can manually create slaves, but they are never created automatically.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
