Seems no one else is getting this as a recurring issue? On some projects, the effect has become so bad that Jenkins is becoming unreliable for us to use (almost 50% of builds fail with this error). It seems like it got worse over time during the last three or four months, but I'm not sure the Jenkins upgrade was the trigger.

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.

Reply via email to