[JIRA] (JENKINS-59959) The Concurrency Limit is not always respected.

[codey.wh...@gmail.com (JIRA)]

Title: Message Title

Codey Whitt commented on JENKINS-59959   Re: The Concurrency Limit is not always respected. From what I can tell, it has to do with how getActiveSlavePods relies on Kubernetes API to tell it what is currently running. There will always be an inherent delay between launch and this showing pods in the API so this approach will likely never be stable. IMO, a singleton that manages the instantiation of the slaves and their states would be the more appropriate solution. I plan to take a look at this next week as it's killing our Jenkins DR automation when our multibranch projects queue up 2k jobs on the first run after scanning. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202763.1572257812000.5828.1579908060253%40Atlassian.JIRA.