This is still an issue, at least as of Jenkins 1.522.

I note that there are two actions you can take for a node:

  1. "mark temporarily offline" which keeps the slave.jar running, but doesn’t send any new jobs to the slave
  2. "disconnect" which means kill the slave.jar process (however, the slave process will be restarted in a few minutes)

There is no option to actually kill the slave process, and stop it restarting.

Also, there is confusion in the Jenkins code about what these options mean. If I "mark temporarily offline", then on the node staus page, it says "disconnected by ...", which is just mixing up two things that are supposed to be distinct.

A rethink of what the options are is needed.

Change By: mwebber (25/Feb/14 10:38 AM)
Resolution: Not A Defect
Status: Closed Reopened
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to