[
https://issues.jenkins-ci.org/browse/JENKINS-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162615#comment-162615
]
Yuu Yamashita commented on JENKINS-8617:
----------------------------------------
oh, i just created my version of the patch but it is a duplication of this
issue :(
https://github.com/jenkinsci/ec2-plugin/pull/18
IMHO, putting security group configuration in SlaveTemplate is good idea since
some AMIs may require distinct security group.
> 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
