Hi,
I faced a similar issue today on a debian server.
We had some nework problems yesterday. Master was not able to
communicate with the slaves.
After the network establishment the jobs where still stuck.
I tried to reeboot server & slaves but still faced the same issue.
When you stop jenkins a
Dear Jan,
Unfortunately, deleting and recreating the nodes did not help in my
case. I am using Linux and not Windows, so the second solution does
not seem to be what I could use.
Regards,
Daniel
On Mar 20, 1:01 pm, Jan Seidel wrote:
> Hi Daniel,
>
> I have had a similar issue some weeks ago.
>
.
Matthew
> -Original Message-
> From: jenkinsci-users@googlegroups.com
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Daniel
> Tkatch
> Sent: 20 March 2012 11:55
> To: Jenkins Users
> Subject: Re: Restricted job keeps waiting even though the node becomes
> avai
Hi Daniel,
I have had a similar issue some weeks ago.
The jobs tied to a specific got stuck for infinite time but the node
was available. Also the configuration was fine. Actually did nothing
change.
I have been researching and troubleshooting quite a while and learned
that deleting and recreating
Now the stuck job got released when I deleted a job that was after it
in the queue. The jobs seem to get stuck in packs, never alone.
On Mar 20, 12:45 pm, Daniel Tkatch wrote:
> Recently, I am experiencing a weird issue.
>
> I have a job whose execution is restricted to a specific node. This
> jo
Recently, I am experiencing a weird issue.
I have a job whose execution is restricted to a specific node. This
job keeps waiting in the queue even though the node became active. It
seems to be stuck in the queue for a while (several minutes) and gets
released after some time. Hmm..
Any idea what
