On Thu, Feb 28, 2019 at 2:47 PM Ivan Fernandez Calvo <[email protected]> wrote: > when we spin more than 100 agents at the same time, […] pipelines try to > reuse an agent because the way we manage to put the agent offline and destroy > (about 1-2% of times)
So, some sort of race condition? Probably depends on what APIs you are using to take the agents offline. `OnceRetentionStrategy` is supposed to work for this case. A much more efficient and less flaky approach is to bypass the `Queue` altogether, as the `dockerNode` step does, though this means you cannot use an unmodified `Jenkinsfile`. -- 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/CANfRfr0KiB2cEv4eo4GDLCOAHtNUSYtEJAZkabYe9ZvQs_%3D3TQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
