May need to extend core to support advertising it. If it's more than 100ms it is likely a new round
On Fri 21 Jul 2017 at 19:56, Martin Weber <[email protected]> wrote: > Am Donnerstag, 20. Juli 2017, 21:01:13 CEST schrieb Stephen Connolly: > > On Thu 20 Jul 2017 at 19:13, Martin Weber <[email protected]> > wrote: > > > > If 1:400 is too high, you'll need to bite the bullet and sort out the > > concurrency to determine when a round starts and then only allow one per > > round to be unblocked (pick a different one each round) > > How can I be informed when a round starts? Implement a QueueListener? > > -- > Cd wrttn wtht vwls s mch trsr. > > > -- > 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/6949603.eISL3IcJ9R%40linux > . > For more options, visit https://groups.google.com/d/optout. > -- Sent from my phone -- 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/CA%2BnPnMxpnmDe_xGwo8UAS1%2BvsCKaSMR3QQvu%2BMUifvj3t-QqJQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
