[
https://issues.jenkins-ci.org/browse/JENKINS-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162814#comment-162814
]
mwhudson commented on JENKINS-8617:
-----------------------------------
The problem with tags, unless I'm misremembering or things have changed, is
that you can't start an instance with a tag, you can only start an instance and
then tag it. So there is a risk of a race there.
But you're right that it's probably a bit silly to use security groups for
that, and there is certainly a case for wanting to have per slave template
security groups rather than per cloud groups.
> 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
