This is probably related to "Build queue hangs after timer task error". It seems
he started a new thread now that he knows the reason of the jenkins build
hanging out.
But I might be wrong and may be something completely different.
Never used the Jenkins plugin, but I thought it created slaves
+1 to Tims answer. Curious as to what are you trying to solve here ? Could you
explain your use case?
punit agrawal
dev-ops lead
new product development, ebay
On 8/10/18, 2:31 PM, "'Tim Hockin' via Kubernetes user discussion and Q"
wrote:
Well, we're not "starting" the pods, we're
Well, we're not "starting" the pods, we're queuing them up for when
nodes become available. Would you rather they get rejected
immediately? what if a node comes online 3 seconds after that
rejection?
On Fri, Aug 10, 2018 at 2:28 PM Basanta Kumar Panda
wrote:
>
> Hi ,
>
> Here is one of the
Hi ,
Here is one of the Scenario
1. K8S Master is up with 2 slave nodes and is configured to jenkins master.
2. Both the slave nodes are down.
3. Job triggered from jenkins and the job is waiting/hanging.
bash-4.2kubectl get nodes
NAME STATUS ROLES AGE
