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

Kubernetes Plugin: Concurrent builds do not have their own unique workspaces

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • kubernetes-plugin
    • None

      Cluster Version: 1.10

      Plugin Version: 1.13.5

      Jenkins Version: 2.159

       

      I am using the kubernetes plugin to dynamically create slaves on a k8s cluster.

      When there are concurrent builds are running of a specific job, they are both using the same workspace which causes all sorts of issues. For example, if I have some cleanUp in my Jenkinsfile, and there are 2 concurrent builds running, if the build 1 finishes first and runs cleanWs(), it deletes everything from that Workspace. Since build 2 is also using the same workspace, build 2 also fails because it lost everything in its workspace ( because they were both using the same workspace ).

       

      This behavior is not correct and it should match the native jenkins behavior when using static slaves.

            Unassigned Unassigned
            agill17 Amrit Gill
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: