I have seen this only when an init.groovy at startup sets the number of executors on the master to e.g. 2 In this scenario it looks like the number of executors have been set in an invalid way (e.g. wrong method in groovy) /Domi
On 22.12.2012, at 19:19, Ido Ran <ido....@gmail.com> wrote: > I basically describe the whole problem in the subject but I'll do it again in > details. > I have a problem with Jenkins (1.480.1) which runs on Windows 7, single node > as Windows Service. > > Jobs are stucked in Build Queue and never start to work. > > The only way to fix it is by going to system configuration and change # of > executors to 0 and apply and then change it again to 2 and save. > > This happen when I restart Jenkins. After I do the change to 0 and 2 > everything start to work normally but it is still a problem. > > Any ideas? > > Thank you, > Ido.
