Next time this is happening, capture a thread dump of the master and all
the slaves by going to the URL:
http:///threadDump
We should be able to tell from the thread dump what the SCM polling thread
is getting blocked on.
-- Dean
On 5/13/13 11:53 AM, "David Shaw" wrote:
>On May 10, 2013, a
On May 10, 2013, at 5:39 PM, Dean Yu wrote:
> On Thursday, May 9, 2013 1:02:58 PM UTC-7, Mandeville, Rob 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 la
On May 9, 2013, at 4:02 PM, "Mandeville, Rob" 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 co
On Thursday, May 9, 2013 1:02:58 PM UTC-7, Mandeville, Rob 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
> ch
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 rea
