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

I also saw this issue occur repeatedly, as soon as we moved to dynamic slaves.
In case anyone else runs into this, our solution was to add a minor source tweak to remove the requirement that the slave which ran the job using the join-plugin persist until the join plugin downstream project is triggered. I believe this requirement was added when support for CopyArchiver was added. Since we dont use CopyArchiver plugin, this was a simple mod:
Our solution was to edit src/main/java/join/JoinAction.java
and change