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

PIpeline job ignores custom workspace location

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      After last update (not sure which one, everything worked last time on 4. nov 2016) pipeline job began to use local jenkins directory (c:/Users/jenkins/.jenkins) for workspaces completely ignoring settings set under: "Manage Jenkins / Worspace Root DIrectory" and "Manage Jenkins / Build Record Root Directory", which are configured as follow:

      Workspace Root Directory = d:/jenkins/ws/$

      {ITEM_FULLNAME}/work
      Build Record Root Directory = d:/jenkins/ws/${ITEM_FULLNAME}

      /builds

        Attachments

          Issue Links

            Activity

            Hide
            noodle_rebellion Dmitriy Belyaev added a comment -

            I completely agree with Zach Swanson on:

            Moreover, if the jenkins config has an option to set a workspace to a particular location than that location should be respected even on the master.

            The plugin should respect global Jenkins settings and use its values.

            And Jesse Glick I was trying to avoid going onto personalities, but as one of the lead developers of this plugin, please stop marking this issues as RESOLVED or DUPLICATE and find some time to understand why it is not working for everyone (I think previous posters explained it in details already).

            Because currently all the communications can be shortly described as: "We decided it to be this way. Accept it or get lost."

            Show
            noodle_rebellion Dmitriy Belyaev added a comment - I completely agree with Zach Swanson on: Moreover, if the jenkins config has an option to set a workspace to a particular location than that location should be respected even on the master. The plugin should respect global Jenkins settings and use its values. And Jesse Glick I was trying to avoid going onto personalities, but as one of the lead developers of this plugin, please stop marking this issues as RESOLVED or DUPLICATE and find some time to understand why it is not working for everyone (I think previous posters explained it in details already). Because currently all the communications can be shortly described as: "We decided it to be this way. Accept it or get lost."
            Hide
            jglick Jesse Glick added a comment -

            From the description it appears to be a duplicate of the known issue which was recently fixed, so you just need to update your plugins.

            Show
            jglick Jesse Glick added a comment - From the description it appears to be a duplicate of the known issue which was recently fixed, so you just need to update your plugins.
            Hide
            noodle_rebellion Dmitriy Belyaev added a comment -

            Jesse Glick oh, I see. I found this original issue and PR on it (which this defect duplicates). I will try to update my plugins. Thanks.

            Show
            noodle_rebellion Dmitriy Belyaev added a comment - Jesse Glick oh, I see. I found this original issue and PR on it (which this defect duplicates). I will try to update my plugins. Thanks.
            Hide
            akmjenkins ASHOK MOHANTY added a comment -

            Quick question.. We are using Jenkins 2.121.3 (& planning to upgrade to 2.164.3). Can I use custom workspace in Multibranch/Script pipeline !? 

            Show
            akmjenkins ASHOK MOHANTY added a comment - Quick question.. We are using Jenkins 2.121.3 (& planning to upgrade to 2.164.3). Can I use custom workspace in Multibranch/Script pipeline !? 
            Hide
            jglick Jesse Glick added a comment -

            Just use the dir or ws steps as needed.

            Show
            jglick Jesse Glick added a comment - Just use the dir or ws steps as needed.

              People

              Assignee:
              jglick Jesse Glick
              Reporter:
              noodle_rebellion Dmitriy Belyaev
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: