|
||||||||
|
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.

Same problem with 1.509.1 LTS.
We are using two Jenkins instances with the same version right now, and this issue seems to affect only the one where the builds are executed on slaves only. Additionally only builds which where renamed and are triggered automatically by croned upstream projects are having this issue.
The only thing I noticed in the logs was the following: