I have Jenkins on a linux server and I want to set up slave on windows virtual machine.
I created simple slave node, with launch method: JNLP.
There is no firewall on the windows machine.
I can connect both via ssh, also I can connect from linux to windows on port 52263 and from windows to linux on port 135.
Still when I try to launch the slave, it cannot be connected.
What should I check? Where could be the problem?
Then I try to connect windows slave I have to open ports at Linux firewall and set static TCP port for JNLP agents at http://jenkinsurl:8080/configureSecurity/
Also you can see extra errors at windows java console.
Choose "Launch Method as Launch agent via Java Web Start" and provide proper "Remote root directory". For more information, please go through https://wiki.jenkins-ci.org/display/JENKINS/Step+by+step+guide+to+set+up+master+and+slave+machines
Related
On my office desktop machine, I'm running a docker container that accesses the GPU. Now, since I'm working from home, I'm connected through ssh to my office desktop computer in vs code via remote ssh plugin which works really well. However, I would like to further connect via remote containers to that running container in order to be able to debug the code I'm running in that container. Failed to get this done yet.
Anyone has any idea if this is possible at all and in case any idea how to get this done?
Install and activate ssh server in a container.
Expose ssh port via docker
create user with home directory and password in container
(install remote ssh extension for vs code and) setup ssh connection within the remote extension in vs code and add config entry:
Host <host>-docker
Hostname your.host.name
User userIdContainer
Port exposedSshPortInContainer
Connect in vs code.
Note: Answer provided by OP on question section.
We set up Jenkins running on our mac at address 10.20.xx.xx:8080
From the same mac, using localhost:8080 can access Jenkins
But from other machines in the network
10.20.xx.xx:8080/ doesn't load the Jenkins page.
Yet, we can ping the machine.
How do we configure so it can be accessed from outside?
This was because our systems are behind a proxy. Had to whitelist our Jenkins server IP in the mac
System preferences> Network > Ethernet|Advanced... > proxies > Bypass proxy settings
I am following a course to setup Jenkins pipeline in a Linux VM.
My host machine is MacOS-mojave.
1) I started the CentOs VM via VirtualBox.
2) I SSH ed to the VM via Terminal in Mac with root user.
3) I installed Jenkins in VM. All successful.
4) I checked in a browser in the VM and Jenkins is running in port 8080.
5) I added the VM host name 'osboxes 'to Mac hosts file.
6) I cleared the DNS cache using sudo killall -HUP mDNSResponder
7) Went to the browser and hit osboxes:8080. Safari saying not able to connect.
8) I did nc -vz 192.168.1.13 8080..it says connection refused
9) I did ping 192.168.1.3 from Mac terminal and it is giving me data.
What is the problem here. Please help
In the Virtual Box configure a host only network and assign it to the Jenkins VM. I haven't tried that approach using hostname, but what I do is put a static IP to the VM so I always know it's IP... Then I can put a record on the hosts file.
I am assuming that you are using NAT networking on the VM.
I installed Jenkins in a linux VM using .war file and
it showed "Jenkins is up and running". So I assume it is installed successfully.
Next, when I tried http://localhost:8080, it is showing "Connection Refused".
Also when I tried to do netstat, I am not able to see 8080 port.
So, I guess it is a firewall issue or are there any other settings I am missing.
I'd like to setup Hudson to work with Ant. I am using it for the first time, and when I try:
java -jar hudson.war it starts doing something, but stops on the line:
INFO: JNLP slave agent listener started on TCP port 59204
I am running Windows 7, also the Java Web Start for hudson does not start.
Check if that port is actually reachable from the node. At the node you can try to telnet MASTER_IP 59204. The Hudson master machine may have a firewall that's currently blocking such access.
Hudson by default uses a random port number for each node to connect via JNLP. You can configure it to use a fixed port number. This works well if you have a firewall and only want to expose a limited number of ports for connection from the outside. Go to Manage Hudson and change TCP port for JNLP slave agents to a fixed port number.