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

Ah, if it goes over the same connection as the other traffic then maybe this is a wider (core) issue. I'll make a note to get thread dumps the next time it happens (assuming I get to it before someone else).
Actually it looks we do have the master's stack because it appeared in the logs. Looking at this closer I now feel like I should have submitted this directly against core... For some reason I was under the impression that the copy artifacts plugin was reasponsible for the copy in both directions. :S