|
||||||||
|
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.
I suppose this issue and JENKINS-16679 have the same origin.
After the initial analysis of JENKINS-16679 (I've done it several months ago; hope to find notes), I suspect that it may require a fix inside the Jenkins core.
As a workaround, it is possible to analyze statuses of future tasks instead of sequential "wait" calls against the submitted projects list.