Thanks very much for helping.
Cheers.

On Wed, Mar 7, 2012 at 11:19 AM, Didier Durand <durand.did...@gmail.com>wrote:

> Hi,
>
> You may want to relate the number of executors to the number of cores
> on your jenkins server if it is more or less dedicated to Jenkins
>
> Soon you will also realize that you need to define priorities to sort
> out jobs in the queue: then this plugin gets useful:
> http://wiki.hudson-ci.org/display/HUDSON/Priority+Sorter+Plugin
>
> regards
>
> didier
>
> On Mar 7, 3:06 pm, Nicky Ramone <nixe...@gmail.com> wrote:
> > Thanks! that worked. It's building now. I don't know how it got to the
> > value 0.
> >
> > Do you have any tips for how to choose that number? I don't have any
> slaves
> > right now.
> >
> >
> >
> >
> >
> >
> >
> > On Wed, Mar 7, 2012 at 11:00 AM, Slide <slide.o....@gmail.com> wrote:
> > > Try changing to 1.
> > > On Mar 7, 2012 6:57 AM, "Nicky Ramone" <nixe...@gmail.com> wrote:
> >
> > >> This is an install that has been there for a long time.
> > >> The "# of executors" is 0.
> > >> Does that mean it's unlimited?
> >
> > >> On Wed, Mar 7, 2012 at 10:53 AM, Slide <slide.o....@gmail.com> wrote:
> >
> > >>> Is this a new install of Jenkins? Or one that's been up for a while?
> How
> > >>> many executors do you have defined in the global config?
> > >>>  On Mar 7, 2012 6:49 AM, "Nicky Ramone" <nixe...@gmail.com> wrote:
> >
> > >>>> That seems to be a different problem.
> > >>>> I haven't defined any quiet periods, and I'm only trying to run one
> > >>>> single build right now. The job never starts.
> >
> > >>>> On Wed, Mar 7, 2012 at 10:41 AM, <matthew.web...@diamond.ac.uk>
> wrote:
> >
> > >>>>>  This is probablyhttps://
> issues.jenkins-ci.org/browse/JENKINS-12994- vote for that ticket if it is
> a problem for you (and/or add a note to
> > >>>>> the ticket indicating that you are also experiencing it) ****
> >
> > >>>>> ** **
> >
> > >>>>> *From:* jenkinsci-users@googlegroups.com [mailto:
> > >>>>> jenkinsci-users@googlegroups.com] *On Behalf Of *Nicky Ramone
> > >>>>> *Sent:* 07 March 2012 13:34
> > >>>>> *To:* jenkinsci-users@googlegroups.com
> > >>>>> *Subject:* Cannot build any jobs: "Pending - Waiting for next
> > >>>>> available executor"****
> >
> > >>>>> ** **
> >
> > >>>>> Hi****
> >
> > >>>>> ** **
> >
> > >>>>> Since several days I'm unable to build anything and I can't
> understand
> > >>>>> what's wrong.****
> >
> > >>>>> Jenkins keeps waiting for an available executor but never
> starts:****
> >
> > >>>>> ** **
> >
> > >>>>> The server has enough free space and memory.****
> >
> > >>>>> I tried restarting Jenkins, upgrading to the latest version (now
> I'm
> > >>>>> on 1.454), restarting the job, but still nothing.****
> >
> > >>>>> I also looked at the catalina.out logs but found nothing related to
> > >>>>> that.****
> >
> > >>>>> ** **
> >
> > >>>>> Maybe someone can give me a hint, please?****
> >
> > >>>>> Thanks in advance.****
> >
> > >>>>> --
> >
> > >>>>> This e-mail and any attachments may contain confidential, copyright
> > >>>>> and or privileged material, and are for the use of the intended
> addressee
> > >>>>> only. If you are not the intended addressee or an authorised
> recipient of
> > >>>>> the addressee please notify us of receipt by returning the e-mail
> and do
> > >>>>> not use, copy, retain, distribute or disclose the information in or
> > >>>>> attached to the e-mail.
> > >>>>> Any opinions expressed within this e-mail are those of the
> individual
> > >>>>> and not necessarily of Diamond Light Source Ltd.
> > >>>>> Diamond Light Source Ltd. cannot guarantee that this e-mail or any
> > >>>>> attachments are free from viruses and we cannot accept liability
> for any
> > >>>>> damage which you may sustain as a result of software viruses which
> may be
> > >>>>> transmitted in or with the message.
> > >>>>> Diamond Light Source Limited (company no. 4375679). Registered in
> > >>>>> England and Wales with its registered office at Diamond House,
> Harwell
> > >>>>> Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE,
> United Kingdom
>

Reply via email to