Thank you to everyone for the cogent replies to my question.
On Wednesday, July 27, 2016 at 4:02:15 PM UTC-4, Baptiste Mathus wrote:
>
> Good practices to scale, IMO:
> * don't build on the master
> * Yes. Add agents/slaves, see below.
> * Never put more than one executor per agent (slave term now
Good practices to scale, IMO:
* don't build on the master
* Yes. Add agents/slaves, see below.
* Never put more than one executor per agent (slave term now deprecated).
Engineering time is far more expensive than having N agents, preventing
builds to step over each other's toes.
** We initially use
-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Bruce Epstein
Sent: July-27-16 14:43
To: Jenkins Users
Subject: Scaling - executors vs slaves
Hi -
I'm an experienced Jenkins user (writing Ant scripts, using plugins, etc.) but
not an IT/administrator, and my IT
You really want a few build agents.
FTR you are not even close to scaling limits... I'm giving a talk on how to
scale Jenkins at this years Jenkins World... I don't want to spoil the fun
of that talk so I'm not giving out details, but if you cannot get to
Jenkins World it will be available on-line
, July 27, 2016 2:43 PM
To: Jenkins Users
Subject: Scaling - executors vs slaves
Hi -
I'm an experienced Jenkins user (writing Ant scripts, using plugins, etc.) but
not an IT/administrator, and my IT dept is not that familiar with Jenkins
scaling.
If anyone can point me to a comprehe
Hi -
I'm an experienced Jenkins user (writing Ant scripts, using plugins, etc.)
but not an IT/administrator, and my IT dept is not that familiar with
Jenkins scaling.
If anyone can point me to a comprehensive discussion of the best way to
scale, please provide a url.
Current architecture:
O
