How To Add Jenkins Controller & Agent Node for Windows | Jenkins Tutorials | Part 6

In this video, learn how to add Jenkins controller & Jenkins agent node for Windows.

- Jenkins agents are machines to whom Jenkins controllers can delegate the task of building projects distributed across different platforms that support Java. It allows multi-platform build and testing using the same Jenkins Server.
- An agent node might be a windows machine, a Linux machine, or some other platform that supports Java; this allows multi-platform build and testing using the same Jenkins server.

You will also learn
🔸 How does Jenkins connect to Windows agent?
🔸 Where does Jenkins agent run?
🔸 How does Jenkins agents work?
🔸 How do you deploy Jenkins agent and connect it to Jenkins master?

Ｖɪᴅᴇᴏ Ｃʜᴀᴘᴛᴇʀꜱ
0:00 Introduction to Jenkins Tutorial for Beginners
0:40 Problems with single Jenkins Server and Need for Jenkins Controller-Agent setup
1:10 Jenkins Controller/Agent (Master/Slave) Architecture
2:03 How to add a Jenkins Controller Node
5:25 How to add a Jenkins Windows Agent Node for Local system setup
7:38 Configuring the global security to activate the local Windows Jenkins Agent Node
10:00 Testing the Jenkins Controller/Agent setup for Windows
11:48 Conclusion

**𝑪𝒐𝒎𝒑𝒍𝒆𝒕𝒆 𝑷𝒍𝒂𝒚𝒍𝒊𝒔𝒕**

The above Jenkins tutorial for beginners for testing covers the Jenkins introduction, Jenkins basics, what is Jenkins and how it works, installation, configuration on a local machine, Jenkins and GitHub integration, scheduling Jenkins, creating Jenkins job for a maven project, Jenkins controller and Jenkins agent nodes for the distributed build, Jenkins pipelines, automated cross-browser testing, Jenkins pipeline, and much more insights on Jenkins for beginners.

**𝑹𝒆𝒍𝒂𝒕𝒆𝒅 𝑩𝒍𝒐𝒈𝒔**

What else?
+ Test website on 2000+ mobile and desktop browser environments over LambdaTest cloud
+ 100 minutes of free automated testing
+ Sessions with 10 Minutes of Each Free Live Interactive testing per month
+ 10 Responsive Testing across 56 Device configurations with a single click
+ 30 minutes of free testing on LT Browser

**𝑬𝒙𝒑𝒍𝒐𝒓𝒆**
📢 FREE For Limited Time Only 🕑, Enroll Now! 👈

**𝑺𝒐𝒄𝒊𝒂𝒍**

#jenkinstutorial #jenkinscontroller #jenkinsagent #testing #jenkins #automation #javascript #developers

Disclaimer:
This video features materials protected by the Fair Use guidelines of Section 107 of the Copyright Act. All rights reserved to © 2021 LambdaTest. Any illegal reproduction of this content will result in immediate legal action

[bootmood]

The problem statement is soooo true. I’d heard about the Jenkins agent’s structure but never got around to hit this up. Now, I know!

[meta]

After two years still very helpful! Thank you, that was the easiest working explanation I have found to set up my windows agent :)

[emmanuelowoeye]

Spent hours trying to figure this out on my own. Armed with this video, it was 30 minutes. Thanks!

[clemensmacho]

I feel like part of the video is missing because we don't see when you create the azure-agent node in the Jenkins configuration, and later at 6:12 you say you will use "the same remote root directory" but we have not seen you use do this before.
Edit: Turns out the part that is missing from this video is actually in the next video.

[joepaduano]

( ) CENTOS Linux "master", + Windows "slave node"
== I installed a service on the windows machine so it would run agent/slave cmd "in the background"
== There is an AD User that's running that service (on the win box)
== & that same user is on my Linux master (in sudo file)
== So that's essentially doing the same thing as the ssh connect - - - am thinking bout that right?

[nemka]

Hi, why did you configure SSH if you used: 'Launch agent by connecting it to the controller'? thanks

[BMXagent]

Hello not sure how you got this working over port 50000 when your Azure Controller only has port 22 open public. I have the same setup and the only way it will work is if port 50000 is open from controller side. Other wise i get the 404 error ... Please let me know how this worked with out that port open .. If I switch that 50000 port to 22 it will not work as well with the same 404 error not found.

[peterwoo]

I'm wondering if ssh is the only bridge between agent and controller node?

[jgc]

Im confused, it doesnt look like you used ssh to connect to windows node.

[amaankhan]

This is really helpful and amazing. I did the same. However I am getting the below error when running the jenkins job.
java.io.IOException: Remote call on JNLP4-connect connection from {jenkins ip} failed

Any idea what might be causing this?