[
https://issues.jenkins-ci.org/browse/JENKINS-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162627#comment-162627
]
mwhudson commented on JENKINS-8617:
-----------------------------------
I'm not sure really -- and I'm not administering Jenkins myself any more, so
I'm might not to be able to contribute any useful thinking here.
IIRC, one of the reasons I wanted to put it onto the cloud was that I wanted to
be able to count the instances Jenkins has launched by checking the security
group. We've had issues where Jenkins has refused to launch instances because
there have been other instances launched by the same account and they are
currently counted against the cap. If the jenkins-launched instances had a
distinct security group, a more accurate count of how many instances have been
launched by jenkins would be possible.'
> cannot customize security group to launch slaves into
> -----------------------------------------------------
>
> Key: JENKINS-8617
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8617
> Project: Jenkins
> Issue Type: Improvement
> Components: ec2
> Reporter: mwhudson
> Assignee: mwhudson
> Priority: Minor
>
> It's slightly inconvenient to have to use the 'default' security group for
> our slaves.
> It's only slightly inconvenient, but it seems that this should be pretty easy
> to fix, too. I may even try myself!
--
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
