On May 9, 2013, at 4:02 PM, "Mandeville, Rob" <[email protected]> wrote:
> I believe that the behavior you are seeing is by design. The concurrent > builds checkbox allows you to run multiple instances of that job at all, but > the SCM poller will only launch one at a time. Basically, with the checkbox > you could kick off as many builds as you wanted manually. > > If you really want to be able to launch a build at 12:30 in the below case, > you need two jobs. > > Job A monitors SCM, and when it sees an SCM change, it launches job B. > > Job B doesn't monitor SCM at all. It lets job A kick it off, grabs sources > from SCM, and goes to work on it. You will need the concurrent build flag on > this one. Thank you very much for this workaround! It solves the problem. I wonder though - is this behavior recent? Unless I'm quite confused, having multiple concurrent builds triggered by polling worked in the past. David -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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/groups/opt_out.
