...@googlegroups.com ] *On Behalf Of *Sami Tikka
> *Sent:* 09 March 2012 05:07
> *To:* jenkins...@googlegroups.com
> *Subject:* Re: Cannot build any jobs: "Pending - Waiting for next
> available executor"
>
>
>
> I got this exact same problem after upgrading to 1.45
.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Sami Tikka
Sent: 09 March 2012 05:07
To: jenkinsci-users@googlegroups.com
Subject: Re: Cannot build any jobs: "Pending - Waiting for next available
executor"
I got this exact same pro
I got this exact same problem after upgrading to 1.453. All my slaves have 1
executor that appeared to be idle but still all the builds just stayed in the
queue.
I downgraded back to 1.451 and problem went away.
-- Sami
Nicky Ramone kirjoitti 7.3.2012 kello 15.34:
> Hi
>
> Since several d
Thanks very much for helping.
Cheers.
On Wed, Mar 7, 2012 at 11:19 AM, Didier Durand 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 pr
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/
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 wrote:
> Try changing to 1.
> On Mar 7, 2012 6:57 AM, "Nicky Ramone" wrote:
>
>> This is
Try changing to 1.
On Mar 7, 2012 6:57 AM, "Nicky Ramone" 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 wrote:
>
>> Is this a new install of Jenkins? Or one that's been up
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 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?
>
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" wrote:
> That seems to be a different problem.
> I haven't defined any quiet periods, and I'm only trying to run one single
> bu
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, wrote:
> This is probably https://issues.jenkins-ci.org/browse/JENKINS-12994 -
> vote for that ticket if it i
This is probably https://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 Nic
11 matches
Mail list logo
