[JIRA] (JENKINS-59019) kubernetes-plugin should allow pre-warming of slaves

[tewing@gmail.com (JIRA)]

Terry Ewing created an issue

Jenkins / JENKINS-59019 kubernetes-plugin should allow pre-warming of slaves Issue Type: Improvement Assignee: Unassigned Components: kubernetes-plugin Created: 2019-08-21 03:07 Priority: Minor Reporter: Terry Ewing When using jenkins kubernetes-plugin each jenkins job in my cluster takes an additional 2 minutes to start. This is due to the job kicking-off a new pod and awaiting the pod to start all containers and register itself with the master. Is there a way to have a pod created and available for the next job? Each of our pipelines is constructed from a slightly different podTemplate() so I understand I would need to have an idle pod for each podTemplate(). Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[edanschwartz@gmail.com (JIRA)]

Edan Schwartz commented on JENKINS-59019

Re: kubernetes-plugin should allow pre-warming of slaves Any updates on this? Or any workarounds you could share?

Add Comment

[tewing@gmail.com (JIRA)]

Terry Ewing commented on JENKINS-59019

Re: kubernetes-plugin should allow pre-warming of slaves

No updates and the only workaround is to go through the pod startup process on each job execution. I'm hoping there's a configuration setting I've missed.

Add Comment

[memotype@gmail.com (JIRA)]

Isaac Freeman commented on JENKINS-59019

Re: kubernetes-plugin should allow pre-warming of slaves

I'd like to see this too, the startup time for agent pods is often longer than the actual builds in our case. We aren't even using pod templates, we just have a unified build environment set as a global pod template in the system settings, so having the ability to keep some number of pods pre-started would greatly accelerate our development cycle.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)