|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
That is an interesting combination of observations. Since the problem is intermittent (at least for me), and does not always happen on the same machine, I'm not sure how I would confidently assure that the updating slave.jar was the solution.
I will certainly investigate my machines to confirm they are all running the current slave.jar.
When I've seen the problem, I was usually able to resolve it by wiping the workspace. A workspace wipe does not touch the changelog.xml file, so I'm a little suspicious that the changelog.xml is not the problem.