Hello all,
I have a Jenkins setup with 1 master and 9 slaves on AWS and using the EC2
Plugin to manage them.
When setting-up my slave I ticked the "Stop/Disconnect on idle" option so
my slaves won't be terminated on idle timeout but rather stopped so it's
faster when rebooting them. However,
va escriure:
>
> 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
&
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 plugin to creat
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
Hi,
I am using Jenkins 1.574 and Amazon EC2 plugin 1.24. Also I had setup the
master executor to zero but when I run the job it not launching new slaves
instead the jobs are showing waiting up in the queue.
On Thu, Aug 21, 2014 at 10:38 PM, jpd4nt jdrawn...@nationaltheatre.org.uk
wrote:
Hi.
Do we also need to set any init script for launching new slave. When I
manually launced the slave to execute the build the slave status is showing
idle and it not able to execute the job.
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To
Hi,
I have installed ec2 plugin and I configured jenkins master to trigger
slaves automatically and I executed 3 builds along with that I run commands
on the server to spike the cpu load but still no slave has been launched.
Please help
Many Thanks
--
You received this message because you
Hi.
Can you post what version of Jenkins you are using and what version of ec2
plugin you are using.
Also have you set the master to have zero executors, that will force the jobs
to run on a slave
--
You received this message because you are subscribed to the Google Groups
Jenkins Users
large repositories, pull times of repositories can be time
consuming when initial pull is performed.
Stefan
sent from mobile.
On Aug 3, 2012 10:16 PM, R. Tyler Croy ty...@monkeypox.org wrote:
On Mon, 16 Jul 2012, Tisch wrote:
Hi all,
I have been looking at the jenkins ec2 plugin for jenkins
repositories, pull times of repositories can be time
consuming when initial pull is performed.
Stefan
sent from mobile.
On Aug 3, 2012 10:16 PM, R. Tyler Croy ty...@monkeypox.org wrote:
On Mon, 16 Jul 2012, Tisch wrote:
Hi all,
I have been looking at the jenkins ec2 plugin
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. I've
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
12 matches
Mail list logo
