|
||||||||
|
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/d/optout.
The stack trace does look very similar to
JENKINS-24161. It might have been a coincidence that renaming the job fixed the issue for us. That job did not have any problems for the past 4000 builds. We upgraded Jenkins a week ago.I will update the ticket if this issue occurs again with the version 1.576.
Thanks![]()