Need help regarding kill the hung job that is running on Jenkins slave. As the job is hung we cannot able to stop from Jenkins GUI and unable to find any PID (by login to the server) as the Slave.jar itself a process that is running on a slave server.Can anyone help me to kill the particular hung Job?
Note : Need not to do restart of slave , As some other jobs are running on same slave.
Thanks In advance
Related
All,
I am starting the Jenkins agent and STAF process via Crontab at my Ubuntu 14.04. When I executing opentest_cli through Jenkins job that should connect to the STAF process it says that the STAF process not alive although I see the STAF process at "ps -ef". Any idea why?
Thanks to all for helping
I am running a Jenkins server on DCOS as documented here https://docs.mesosphere.com/1.7/usage/tutorials/jenkins/.
The Jenkins server is able to spawn new mesos slaves when new jobs are scheduled and kill them when the job is completed.
But if a cluster node crashes, having a Jenkins job running on it, Jenkins server doesn't re-run the job on other available nodes.
Is the Jenkins service on DCOS fault tolerant?
Can we re-run the job(on some other available node) that failed due to cluster node crashed in between execution of the job?
Jenkins itself does not rerun jobs that disappear. It is not specific to DC/OS or Mesos, it's just the way Jenkins works.
DC/OS and Mesos will make sure that Jenkins stays running and available to send jobs to, and in this way, it is "fault tolerant", but in the way you are asking about it isn't.
I am using ec2 plugin in Jenkins to bring up slaves . I have configured in such a way that the Slaves will die if they are idle for 30 min.
Due to various reasons I want the Slaves to be killed as soon as the build process is completed .
Is there a way to do this ? If so can it be done through pipeline script.
I was using the Restart Safely option in jenkins to restart the master after some running jobs completed.
However jenkins was unattended after that and now it's up and running. Is there a way to check when the master restarted in the form of jenkins reboot history (or something like ps -ef equivalent would also work in that I can see the process start time to get details of the restart).
It will be in /var/log/jenkins/jenkins.log.log.
Check for Jenkins is fully up and running you should also see messages about the scheduled reboot.
I configured Jenkins Slave and created a job to run in slave.
After triggering the job , if I am stopping it in Jenkins it showing the Job has been stopped.
But in the node still script is still running.
I noticed that too. see also JENKINS-6188