while running the jenkins job I got above error, I found jenkins agent is active and connected to master. we used linux vm as a jenkins-agent(docker2). Java version is 1.8.0_222, jenkins version is 2.332.3. Please check the above error for more details.
I tried updating java version, restarted jenkins agent by killing jenkins process on vm, rebooted the respected vm(docker2) ,updated jenkins git plugin , ping the master node from agent node (docker), curl the git repo from agent machine (docker2).
Expecting to able to call docker2 agent and complete job configuration as expected.
please help me out of this, thank you in advance
Related
I need to connect my Jenkins to remote server as well. I have tried with agent slave method, but not working. Any Suggestion will be appreciated.
I was using Jenkins 1.7.4 version in RHEL Linux server. I can able to configure the slave using "launch agent via execution of command on the master" option during slave setup.
Now we have upgraded jenkins to 2.121.1 version. Now we unable to find that option in the upgraded version.
How to fix this issue.
Manually I Installed command-launcher, jdk-tools plugin. Then it works.
I just started using Jenkins. Still not familiar with all its features.
I would like to run a Ranorex test which is on a remote computer. How can I do that from Jenkins?
To execute binaries on a specific host, you can use slaves.
Here is a guide to setup master and slave on windows:f
https://wiki.jenkins-ci.org/display/JENKINS/Step+by+step+guide+to+set+up+master+and+slave+machines+on+Windows
You will run the slave on the remote computer and connect it to the master.
To run the slave on your remote computer, you have to download the slave.jar and start it on the remote computer. This is described in the wiki article above.
You have to ensure, that your job is executed on the slave. This can be done by labels. You configure a label on the slave and configure the same label on the job too.
Via SSH slave plugin, we can have Jenkins slave to run specific job, but in my understanding, only SSH is enough to execute commands, why Jenkins still want to run slave.jar(Have to install JAVA)?
SSH is the communication mechanism between the master and slave machines.
The slave still has to run something to listen to the master and to do the actual builds. That Jenkins slave code is written in Java and stored in slave.jar.
So the reason you need Java on the slave machine is because the Jenkins slave software is written in Java. SSH is used by the master to tell the slave to do something.
We have a master Jenkins running on a Linux system. The same master is attached as node using "Launch slave via execution of a command on the master". It has the same FS root as the JENKINS_HOME. The command is ssh "machine_name" "shell_script"
The shell script gets the latest slave.jar and runs it.
The master has 0 executors. The node has been given 7. I'm seeing weird behavior in the builds, like workspaces being deleted once a day, etc. I'm not sure if this is related to the way the Jenkins Master-slave is configured.
Any ideas if this is a supported configuration?