> On 21. Jul 2020, at 23:05, 'Martin Schmude' via Jenkins Developers
> <[email protected]> wrote:
>
> This reminds me of that I am worried from time to time by the terms "agent"
> and "node".
> They seem to be synonyms - am I right?
> If so, shouldn't "agent" be the preferred term, due to the decision of 2016
> and "node" be dropped?
>
These terms are useful and consistent, as master can also be a node. By
default, it's even the only node.
So "node" is an term for "master and agents" (at least the "executing
workloads" part of master, see my and others' feedback to the ongoing
terminology update that it could make sense to use different terms here).
> to me, node = executor, but not really
One node can have multiple executors. Executors are individual slots for a
single workload.
By default, a new Jenkins installation has 1 node (the master) with 2
executors, and 0 agents.
All of that is also explained in https://www.jenkins.io/doc/book/glossary/
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/9636A16D-1011-47E7-BCEE-A6738024B660%40beckweb.net.
