Stephen, I remember you mentioning it a JIRA ( which I can't seem to find now for the life of me) that Cloudbees Jenkins runs some sort of 'deadlock killer' on a timer .
Is my memory serving me right about this? Do you have that in a plugin somewhere if so? Surya On Monday, October 17, 2016 at 9:53:23 AM UTC-5, Surya Gaddipati wrote: > > Hi all, > > I am working on plugin > <https://github.com/suryagaddipati/jenkins-docker-swarm-plugin> that > creates a single use computer/node whose lifecycle is tied to a single > build . I am currently adding the node like this > > Jenkins.getInstance().addNode(node); > > > However that method requires multiple Queue locks while doing so. > > > I believe in my particular case there is no need for queue locking since > only a single build can ever be scheduled on the computer via > LabelAssignmentAction. > > I wanted to check , > > 1. if that assumption is correct > > 2. If the team is open to accepting a patch to jenkins.instance for a new > method which adds a node without the Queue lock. > > > Thank you. > > > --Surya > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3d00dd3a-15cd-485c-937b-86f99182ecf4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
