[
https://issues.jenkins-ci.org/browse/JENKINS-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163048#comment-163048
]
SCM/JIRA link daemon commented on JENKINS-8617:
-----------------------------------------------
Code changed in jenkins
User: Francis Upton
Path:
pom.xml
src/main/java/hudson/plugins/ec2/SlaveTemplate.java
src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly
src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java
src/test/java/hudson/plugins/ec2/TemplateLabelsTest.java
http://jenkins-ci.org/commit/ec2-plugin/543777c6f79adaf243df931bfffda6d3a86ca5f7
Log:
Merge pull request #18 from yyuu/master
JENKINS-8617 cannot customize security group to launch slaves into
Compare: https://github.com/jenkinsci/ec2-plugin/compare/d96e049...543777c
> 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: Yuu Yamashita
> 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
