<blockquote>
<p>Q1. Should we be executing these steps on node or a machine which we
want to designate as agent?</p>
</blockquote>
<p>You can execute them where ever you want. If you want the agent to run on your local machine, then run it locally. If you want the agent to run on the same hardware as the Jenkins Controller then run the docker command on the Jenkins machine. If you want to run it on a cloud or in a Kubernetes pod, then run the command their.</p>
<blockquote>
<p>Q2. Above is nothing but the Jenkins controller UI right?</p>
</blockquote>
<p>Yes</p>
<blockquote>
<p>But above UI does not seem to accept IP address of the agent node on
which we staarted docker agent.</p>
</blockquote>
<p>It has a <code>Host</code> field. Put the IP address or hostname into it.</p>
<blockquote>
<p>Q3. Does Jenkins controller automatically discovers running agents
reachable on the network?</p>
</blockquote>
<p>No, that is what the above controller UI page is for. You are telling Jenkins, this is how to connect to an agent.</p>
<blockquote>
<p>Q4, Q4.1, Q4.2</p>
</blockquote>
<p>These should really be a new question but I will give you a brief explanation.</p>
<p>Agents and plugins are not really related. Plugins are installed on the Jenkins controller and will run where you run your job/pipeline. So this could be on the controller or on an Agent. Also plugins can help you setup agents, like the <a href="https://plugins.jenkins.io/ec2/" rel="nofollow noreferrer">Amazon Ec2 plugin</a>.</p>
<p>Jenkins can be tough to learn but it is the most powerful CICD engine that exists as long as you use scripted pipelines. Another place that might be helpful is <a href="https://community.jenkins.io/" rel="nofollow noreferrer">https://community.jenkins.io/</a></p>

CC BY-SA 4.0
2022-07-18T22:30:13.947Z
2022-07-18T22:30:13.947Z
Levi
<p>I was trying to understand jenkins agents. This page asks to first <a href="https://www.jenkins.io/doc/book/using/using-agents/#creating-your-docker-agent" rel="nofollow noreferrer">create jenkins docker agent</a>. But it doesnt say where to execute these steps?</p>
<p><strong>Q1.</strong> Should we be executing these steps on  node or a machine which we want to designate as agent?</p>
<p><a href="https://www.jenkins.io/doc/book/using/using-agents/#setup-up-the-agent1-on-jenkins" rel="nofollow noreferrer">The next step</a> asks to setup an agent through Jenkins UI:</p>
<p><a href="https://i.sstatic.net/vPO6j.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/vPO6j.png" alt="enter image description here" /></a></p>
<p><strong>Q2.</strong> Above is nothing but the Jenkins controller UI right?</p>
<p>But above UI does not seem to accept IP address of the agent node on which we staarted docker agent.</p>
<p><strong>Q3.</strong> Does Jenkins controller automatically discovers running agents reachable on the network?</p>
<p><strong>Q4.</strong> What are exactly Jenkins plugins in relation with agents? Jenkin glossary <a href="https://www.jenkins.io/doc/book/glossary/#plugin" rel="nofollow noreferrer">defines plugin </a> as &quot;an extension to Jenkins functionality provided separately from Jenkins Core.&quot; But that does not explain much of its nature or functionality. <a href="https://www.jenkins.io/doc/book/managing/plugins/" rel="nofollow noreferrer">This page</a> also explain plugin installation and management on the controller, but doesnt explain exact nature of their functionality.</p>
<p><strong>Q4.1.</strong> Do plugins run jobs of agent nodes? For example, does <a href="https://plugins.jenkins.io/android-emulator/" rel="nofollow noreferrer">Android Emulator</a> plugin installed on controller installs and runs android emulator on available agent?</p>
<p><strong>Q4.2.</strong> If yes is the answer to Q4.1, does every plugin need corresponding process to be installed on the agent so that agent can carry out functionality specified in the pluin on the controller?</p>
<p>PS: Am a noob in Jenkins and overall DevOps stuff and just trying to wrap my head around Jenkins</p>

<jenkins><jenkins-pipeline><jenkins-plugins>
Understanding Jenkins plugins and agent
RajS
# Understanding Jenkins plugins and agent

(Asked by: username_0 on 2022-05-07)

I was trying to understand jenkins agents. This page asks to first [create jenkins docker agent](https://www.jenkins.io/doc/book/using/using-agents/#creating-your-docker-agent). But it doesnt say where to execute these steps?

**Q1.** Should we be executing these steps on node or a machine which we want to designate as agent?

[The next step](https://www.jenkins.io/doc/book/using/using-agents/#setup-up-the-agent1-on-jenkins) asks to setup an agent through Jenkins UI:

[![enter image description here](https://i.sstatic.net/vPO6j.png)](https://i.sstatic.net/vPO6j.png)

**Q2.** Above is nothing but the Jenkins controller UI right?

But above UI does not seem to accept IP address of the agent node on which we staarted docker agent.

**Q3.** Does Jenkins controller automatically discovers running agents reachable on the network?

**Q4.** What are exactly Jenkins plugins in relation with agents? Jenkin glossary [defines plugin](https://www.jenkins.io/doc/book/glossary/#plugin)  as "an extension to Jenkins functionality provided separately from Jenkins Core." But that does not explain much of its nature or functionality. [This page](https://www.jenkins.io/doc/book/managing/plugins/) also explain plugin installation and management on the controller, but doesnt explain exact nature of their functionality.

**Q4.1.** Do plugins run jobs of agent nodes? For example, does [Android Emulator](https://plugins.jenkins.io/android-emulator/) plugin installed on controller installs and runs android emulator on available agent?

**Q4.2.** If yes is the answer to Q4.1, does every plugin need corresponding process to be installed on the agent so that agent can carry out functionality specified in the pluin on the controller?

PS: Am a noob in Jenkins and overall DevOps stuff and just trying to wrap my head around Jenkins

**Tags:** jenkins, jenkins-pipeline, jenkins-plugins


---

## 1 answers

### Answer by username_1 on 2022-07-18. Score: 0

> Q1. Should we be executing these steps on node or a machine which we
> want to designate as agent?

You can execute them where ever you want. If you want the agent to run on your local machine, then run it locally. If you want the agent to run on the same hardware as the Jenkins Controller then run the docker command on the Jenkins machine. If you want to run it on a cloud or in a Kubernetes pod, then run the command their.

> Q2. Above is nothing but the Jenkins controller UI right?

Yes

> But above UI does not seem to accept IP address of the agent node on
> which we staarted docker agent.

It has a `Host` field. Put the IP address or hostname into it.

> Q3. Does Jenkins controller automatically discovers running agents
> reachable on the network?

No, that is what the above controller UI page is for. You are telling Jenkins, this is how to connect to an agent.

> Q4, Q4.1, Q4.2

These should really be a new question but I will give you a brief explanation.

Agents and plugins are not really related. Plugins are installed on the Jenkins controller and will run where you run your job/pipeline. So this could be on the controller or on an Agent. Also plugins can help you setup agents, like the [Amazon Ec2 plugin](https://plugins.jenkins.io/ec2/).

Jenkins can be tough to learn but it is the most powerful CICD engine that exists as long as you use scripted pipelines. Another place that might be helpful is <https://community.jenkins.io/>


---

