|
||||||||
|
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/groups/opt_out.
I'm so happy that I found that bug. I couldn't upgrade to jenkins 1.519-1.523, no linux slaves were running (windows slaves were fine) and I couldn't figure out what the issue was. Now I see that it was because of my .jenkins script in home directory of build user (and we have mounted home directories - so it is the same directory on all hosts). After renaming the script and changing all jobs which using it upgraded jenkins is working ok. Hopefully this cache directory wouldn't be messed up because many hosts are using it.