On Mon, May 5, 2014 at 2:42 PM, Stephen Connolly
<[email protected]> wrote:
>
> It is rather easy to saturate a server with a small number of ssh-slaves
> based slaves.
>
> For example, on an AWS m3.large class machine, 10 ssh-slaves concurrently
> building jobs as chatty as the mock-load-builder job type is the most you
> can push.
>
> If you use JNLP slaves, you can get close to 60 concurrent builds before the
> system starts falling over.
So is there a straightforward way to use ssh to log in and
install/update the slave jar and then run it to connect via jnlp
instead of whatever is so resource-intensive?
--
Les Mikesell
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
