There is a place inside the Advanced settings for an AMI where you can
specific a subnet ID for a VPC. Give it the subnet ID for a specific
already-created subnet inside your VPC, and the instance should show up in
the VPC. The VPC ID itself is not required; it is implied by the subnet ID.
On M
Ping since this might have been lost over the holidays.
For now I've resorted to forking EC2 plugin to avoid this. I'm sure this is
not what you want.
On Wednesday, December 30, 2015 at 4:37:27 PM UTC-8, Michael Barrientos
wrote:
>
> We would like to use Jenkins EC2 plugi
We would like to use Jenkins EC2 plugin to create spot instances for our
tests. We also use the Google Login Plugin, but the login plugin seems to
get int the way of the mechanism that the Spot plugin uses to register
itself; it cannot read the /computer/[slave id]/slave-agent.jnlp file
because
Looks like https://issues.jenkins-ci.org/browse/JENKINS-26508
On Tuesday, January 20, 2015 at 3:44:21 PM UTC-8, Josh Santangelo wrote:
>
> After updating my Jenkins install, I've found myself in this situation:
>
> https://www.dropbox.com/s/xenluffkmjhzi50/Screenshot%202015-01-20%2015.42.13.png
>
