|
||||||||
|
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.
We're seeing an issue with the exact same output. Unfortunately, we are still on Jenkins 1.498 and upgrading right now isn't an option. But looking at the link of where this regressed, it looks like the earliest tag I see is 1.517 - am I reading correctly that this bug wasn't introduced until then so we should be looking elsewhere as to the source of our issue?
If it is this issue, is there anything we can do on the system running Jenkins to try to mitigate it?