Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41071

Pipelined jobs do not execute concurrently with Kubernetes-CI-Plugin

    XMLWordPrintable

    Details

    • Similar Issues:

      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.

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          gsanchezu Guillermo Sanchez Urien added a comment -

          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

          Show
          gsanchezu Guillermo Sanchez Urien added a comment - 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
          Hide
          Permalink
          gsanchezu Guillermo Sanchez Urien added a comment -

          Added provisioning strategy to allow concurrent jobs to run in parallel

          Show
          gsanchezu Guillermo Sanchez Urien added a comment - Added provisioning strategy to allow concurrent jobs to run in parallel

            People

            Assignee:
            gsanchezu Guillermo Sanchez Urien
            Reporter:
            sunshinekitty Alex Edwards
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: