When the EC2 plugin launches an instance from an AMI you specify, you can tell it to 'idle' the instance after some period of time, and you can *also* tell it to stop the instance instead of terminating it. If you do this, then when the instance is required again, it will be started back up (which is fast), run its jobs, then when it goes idle it will be stopped again.
This is pretty much what the OP asked for, except that the EC2 plugin itself
will create the instance from the AMI, rather than it being manually created.
If you never delete the created slave instance, it will stay around forever,
but will only be running (and costing you money) when it has jobs to run or is
in its idle period. There will be some costs for the EBS volume(s) that the
instance uses for its filesystems, but these are quite low and would be present
no matter how you started and stopped it.
----- Original Message -----
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Jan 2 2013 08:43:08
As far as I know, the EC2 instances are not support stop/start, but
reboot.
So you can only terminate the EC2 instances or reboot them.
But you can terminate it and create another one on demand.
james mintram
December 31, 2012 3:00 AM
Hi All,
I wondered if it were possible, or not then a trivial update to the EC2
plugin to allow it to start/stop an instance that already exists.
Currently I have 2 Windows instances, 1 which is 24x7 and is covered in
the free tier but its performance is lacking. The other is a High CPU
instance that compiles code very fast, however I do not want this
running 24x7 due to cost issues, so I have to manually start/stop it
when I want to run a large set of builds.
If there was a way to automatically start and stop an existing instance
given its ID then it finish my CI configuration for now :)
Regards,
James Mintram
--
Adam PAPAI
E-mail: w...@wooh.hu
Phone: +3630 3355735
Web: http://www.wooh.hu
<<inline: compose-unknown-contact.jpg>>
