I have a node which exists in a remote environment. I can access the node via jumphost. The Jenkins instance can access the jumphost. Is there anyway to create a node to access via the jumphost.
Related
The problem is following.
I have Jenkins running on local machine (8080 port).
I've created linux instance in private cloud to use it as slave node for Jenkins.
I'm connecting to this linux node via Putty and logging in.
Trying to download agent.jar file, that needed for node connection using following command:
wget http://<my_ip>:8080/jnlpJars/agent.jar
But everything I get - is Connecting to <my_ip>:8080... Connection timed out.
The IP address has been taken using cmd>ipconfig>Wireless Lan Adapter WiFi>IPv4 Address.
At the same time, I have the VPN running on local machine (otherwise I won't be able to connect to private cloud, where linux node is located). Is it possible that I'm getting incorrect ip via ipconfig?
So what am I doing wrong?
I am just starting with Jenkins, and I am confused on the Remote root directory, the WorkDir and the Internal data directory, precisely on their full path, including Hostname.
The slave is supposed to be on a different node, but I don't see where we can specify a Hostname or IP address.
The examples Remote root directory I have seen so far looks like /var/jenkins, is it on the master node ? if not how or where do we specify the remote Hostname or IP address ?
Same for the Workir, is it remote or local ?
Thanks in advance.
Your jenkins master node can run builds and works as an slave too.
Remote root directory is on the slave.
Manage the slaves is in section "Manage Nodes".
Specify the hostname/IP Address in the launch method option: "via SSH"
To join a slave:
https://medium.com/#chathurams.sa/step-by-step-guide-to-add-jenkins-slave-nodes-f2e756c8849e
I am having Jenkins in my virtual machine Azure .i need to access it with URL remotely from outside.
No matter which the steps you have done, create the VM with a cloud-init file to install the Jenkins, or create the VM and then install the Jenkins. There is no difference.
You need to open port 8080 for Jenkins traffic and port 1337 for the Node.js app. If you finish all the settings of Jenkins, then you can browse the Jenkins with the VM public IP and the port 8080 outside the VM, the URL like this: http://vmPublicIps:8080. Get all the steps from Create a VM in Azure with Jenkins.
Or you can just create a Jenkins Server with the image that Azure provided, see Create a Jenkins server on an Azure Linux VM from the Azure portal.
i have a jenkins that run inside a docker container (on a server A) and i want to publish an artifact over ssh in a server B.
I have installed the plugin "publish over ssh" in Jenkins but i don't know how to configure the ssh.
I guess that i must generate a public/private key on the server A and send my public key on the server B. But for which user?
I have a user jenkins on the server B but not on the server A. Should i generate the key with the same user that run the docker on the server A? Where should I put my keys?
Thanks.
We followed Jenkins's official guide and our master is running as a docker container. I'm now trying to set up another machine as slave for this Jenkins master and I think I need to manually copy the public SSH keys of the master to the new slave machine. How do I access these keys? Isn't it a problem that the Jenkins container that can be destroyed and created many times? It does have a persistent volume container for jenkins data but I'm assuming that's not where the keys are.