--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/142ebe47-dbc5-4bf5-8bf1-96f69517983ao%40googlegroups.com.
Yes, the usages of these terms should cleaned up and made consistent. "agent" is a better term in almost all cases. Sometimes there is a technical distinction between the terms, but we should only use "node" where we really need to distinguish that and use "agent" as much as possible in the UI.
Jeff
--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9636A16D-1011-47E7-BCEE-A6738024B660%40beckweb.net.
I see "the master" as having two contexts. There is the Administrative context (configuration, plugins etc.), that determine focus, capability, delegation. Then there's the context of those tasks that are necessary to execute "on the master". What about the tasks run on master? It's still executors doing the work...
Agent: An agent is typically a machine, or container, which connects to a Jenkins master and executes tasks when directed by the master.
Master: The central, coordinating process which stores configuration, loads plugins, and renders the various user interfaces for Jenkins.
Node: A machine which is part of the Jenkins environment and capable of executing Pipelines or Projects.
Both the Master and Agents are considered to be Nodes.
> By default, a new Jenkins installation has 1 node (the master) with 2 executors, and 0 agents.this sentence has made it the most clear I've ever been about it. Thank you
On Wed, Jul 22, 2020 at 4:41 AM Daniel Beck <m...@beckweb.net> wrote:
> On 21. Jul 2020, at 23:05, 'Martin Schmude' via Jenkins Developers <jenkin...@googlegroups.com> 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 jenkin...@googlegroups.com.