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.
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.
Hey Justin, The NAT rules defined in the template translate an incoming port of 50000 to port 22 (SSH) of the first VM, an incoming port of 50001 to port 22 of the second VM and so on, so to connect to the first VM, SSH to port 50000 of your public IP address.
gr8 video - thank you. I just wanted to run something by you (@Lambda Test) to see if I did this "right". ( ) 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?
Hey Peter SSH is not the only way to establish communication between an agent and a controller node. Jenkins supports various methods of communication including JNLP (Java Network Launch Protocol) and WebSockets, in addition to SSH. The choice depends on your specific setup and needs.
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?
This could be due to refSpec configuration on Jenkins. Please try disconnecting and reconnecting the agent. Please also check the JDK versions on the node and the controller are reasonably close to one another.
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!
Spent hours trying to figure this out on my own. Armed with this video, it was 30 minutes. Thanks!
Great to hear! Emmanuel
After two years still very helpful! Thank you, that was the easiest working explanation I have found to set up my windows agent :)
Glad you liked this😊
Subscribe to our channel to never miss an update on the upcoming tutorials! ✨
simple and sweet explanation...
Thank you so much 🙂
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.
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.
Hey Justin,
The NAT rules defined in the template translate an incoming port of 50000 to port 22 (SSH) of the first VM, an incoming port of 50001 to port 22 of the second VM and so on, so to connect to the first VM, SSH to port 50000 of your public IP address.
gr8 video - thank you. I just wanted to run something by you (@Lambda Test) to see if I did this "right".
( ) 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?
Hi Joe,
Let us get back to you on the same
Im confused, it doesnt look like you used ssh to connect to windows node.
Hey there👋🏻
We used the Jenkins Windows Agent service to establish a connection between the Jenkins controller and the Windows node.
Hi, why did you configure SSH if you used: 'Launch agent by connecting it to the controller'? thanks
I tried and there is no use of ssh keys , seriously from both the ends .
You only need agent.jar and Java installed on agent node
we made the keys for the azure agent
I'm wondering if ssh is the only bridge between agent and controller node?
Hey Peter
SSH is not the only way to establish communication between an agent and a controller node. Jenkins supports various methods of communication including JNLP (Java Network Launch Protocol) and WebSockets, in addition to SSH. The choice depends on your specific setup and needs.
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?
Thanks Amaan, Let us get back to you on this
This could be due to refSpec configuration on Jenkins. Please try disconnecting and reconnecting the agent. Please also check the JDK versions on the node and the controller are reasonably close to one another.