|
||||||||
|
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.
https://github.com/jenkinsci/docker-plugin/blob/master/src/main/java/com/nirima/jenkins/plugins/docker/DockerCloud.java#L166 is wrong since at least 1.448 or so. It should be letting the NodeProvisioner add the node... so I suspect that docker-plugin is amongst the great unwashed of the really bad implementations of cloud plugins that everyone has copy&pasted... and anyway that is a dodgy hack, it should really wait for init script completion is that is a blocker and the bug that the comment claims to be working around should be fixed by now.
https://github.com/jenkinsci/durable-task-plugin/blob/master/src/main/java/org/jenkinsci/plugins/durabletask/executors/OnceRetentionStrategy.java#L70 is just completely wrong... it does not do a two phase removal, and thus can cause race conditions with the queue. I suspect that is where the root cause of this issue lies