When a server is designated as a permanent node, what happens to that server?

[Kiran]

When a server is designated as a permanent node, what happens to that server?  Does Jenkins transfer an installer package or set of configuration files?  If so, where do the files go?  What is the size in KB of these files?  What type of overhead will this server have due to this designation?

With Jenkins 1.x, it was called a Dumb Slave.  I have the same questions for the Dumb Slave.

[Mark Waite]

I think you'll be best served by enabling a slave yourself and then seeking the answers on that system.  You'll learn more, and you're more likely to find answers to the questions that are most relevant to you.

Mark Waite

On Thu, Aug 18, 2016 at 4:53 PM Kiran <catrina...@gmail.com> wrote:

When a server is designated as a permanent node, what happens to that server?  Does Jenkins transfer an installer package or set of configuration files?  If so, where do the files go?  What is the size in KB of these files?  What type of overhead will this server have due to this designation?

With Jenkins 1.x, it was called a Dumb Slave.  I have the same questions for the Dumb Slave.

--
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 jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0c9d1dd5-4eab-471c-8cc5-6f6bf76feedc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kiran]

I already did that.  The answers were not obvious to me.

[Daniel Beck]

> On 19.08.2016, at 00:53, Kiran <catrina...@gmail.com> wrote:
>
> When a server is designated as a permanent node, what happens to that server? Does Jenkins transfer an installer package or set of configuration files? If so, where do the files go? What is the size in KB of these files? What type of overhead will this server have due to this designation?

Typically there's a JAR cache in $HOME/.jenkins (a few MB), and everything else is in the directory you configured ("agent home" I think it's called). Usually, it's a few dozen MB at most, plus tool installations and workspaces.

> With Jenkins 1.x, it was called a Dumb Slave. I have the same questions for the Dumb Slave.

No difference.

[Kiran]

So most of the time (when Jenkins isn't interacting with a permanent agent), there is no extra CPU or RAM utilization from the server having the .jar file and being configured as a permanent agent?

[Daniel Beck]

> On 20.08.2016, at 22:41, Kiran <catrina...@gmail.com> wrote:
>
> So most of the time (when Jenkins isn't interacting with a permanent agent), there is no extra CPU or RAM utilization from the server having the .jar file and being configured as a permanent agent?

While the node is connected/the Java process running, it consumes some memory and CPU, but it should be (for a Java process) fairly modest if there are no running builds.