I've now created my own Groovy script that does this. It is based on this script from the Jenkins wiki, but I don't let it restart nodes automatically. I assume there's a reason why the node online so I'd like to look at it first. I think it's a great template for other states/parameters that we need to monitor.

For example I've added a small check to ensure that the nodes are in sync since we recently had that problem when switching to winter time. Also, my version does not send e-mails if the node is "Disconnected by ..." since I assume that there's a reason why someone disconnected the node manually.

My modifications are so small that there's no point posting the script here. If you want the same solution/workaround, check out the link above and adopt to your needs. It was very easy to expand even without much Groovy knowledge

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

Reply via email to