Have you tried with aws cli console?
I guess you could install it on the jenkins instance and execute the
command line to remotely start an existant instance
http://docs.aws.amazon.com/cli/latest/reference/ec2/start-instances.html
Regards,
El dilluns, 16 juliol de 2012 9:09:44 UTC+2, Tisch va
You could mount a disk which contains a fairly uptodate clone of your repo, and
when you clone, pass this local disk as --reference repo. Works with git, I
don't know about other version control tools.
-- Sami
Stefan Dänzer kirjoitti 4.8.2012 kello 15.28:
> Thanks for your reply. I understan
Thanks for your reply. I understand your concern about not having a clean
host for the build process. However there are a couple of arguments for me
using an instance instead of an ami:
- firing up a new ami is quite more time consuming then booting an already
existing instance.
- when having large
On Mon, 16 Jul 2012, Tisch wrote:
> Hi all,
>
> I have been looking at the jenkins ec2 plugin for jenkins. I've read the
> documentation for the plugin on the plugin page. I can't find a way to set
> an instance-ID
> (i-88e6xxx) instead of an AMI-ID to start slaves. I've seen the option to
> s
bump.
On Monday, July 16, 2012 9:09:44 AM UTC+2, Tisch wrote:
>
> Hi all,
>
> I have been looking at the jenkins ec2 plugin for jenkins. I've read the
> documentation for the plugin on the plugin page. I can't find a way to set
> an instance-ID
> (i-88e6xxx) instead of an AMI-ID to start slaves.
Hi all,
I have been looking at the jenkins ec2 plugin for jenkins. I've read the
documentation for the plugin on the plugin page. I can't find a way to set
an instance-ID
(i-88e6xxx) instead of an AMI-ID to start slaves. I've seen the option to
stop a slave instead of terminating it. So I'm sear
