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

Different behaviour of "Working directory" in 1.4 vs 1.5

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Minor Minor
    • kubernetes-plugin
    • None
    • kubernetes-plugin: 1.4
      kubernetes-plugin: 1.5

      When you omit a value for "Working directory" in v1.4 it defaults to /home/jenkins and does not mount a workspace-volume in /home/jenkins. This gives us the ability to place serveral config files in the jenkins home directory (e.g. docker config) of the used image.

      When you omit a value for "Working directory" in v1.5 it leaves the mountPoint value field blank when it tries to create the container and returns with an error from the k8s server. When i set "Working directory" to /home/jenkins the container will be created but it also mounts an emptyDir in /home/jenkins and overwrites everything in it. 

      Which behavior is working as intended and which is a bug? If the v1.5 behavior is working as intended it would be nice if you add a feature that allows us to disable the workspace-volume mount for the working directory.

            csanchez Carlos Sanchez
            rmarkwitz Robin Markwitz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: