Details
-
Bug
-
Status: Resolved (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
Jenkins 2.19.4
Kubernetes 1.4.7
Jenkins host: https://hub.docker.com/r/jenkinsci/jenkins/
Jenkins slaves: https://hub.docker.com/r/jenkinsci/jnlp-slave/
Description
Issue: When a pipeline job is already running and another is started the second job will try to execute on an existing build slave. This slave is deleted by job #1 after it completes, at which time job #2 will start a new slave to run in.
Desired: The second job in this instance should not wait for an existing slave container, it should create another one given it's under the pod limit.
Hi Alex, thanks for reporting the issue.
We will put it in plan to solve it. However, I cannot commit on any date for it to be completed...
Thanks!
Guillermo