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

Allocate shorter workspace if it will be too long for reasonable use inside build

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
      None
    • Similar Issues:

      Description

      When using rich matrix axes or deep folders hierarchy, substantial part of maximal path name (255 on windows for instance) can be consumed by the path to workspace not leaving enough room for the build itself.

      Introduce threshold (global or per job) to define expected path length left for build. if the default allocation algorithm creates WS path so long that there will be not enough path length left for the build, hash should be used instead.

      Therefore, if the threshold will be configured to 1024 Jenkins will use hash on Windows all the time and on linux only if the workspace path exceeds 3072 characters (assuming 4096 is the maximal path allowed on linux).

        Attachments

          Issue Links

            Activity

            Hide
            ssbarnea Sorin Sbarnea added a comment -

            Any change of having this fixed, ever, at least for normal pipelines?

            Here is one real life example: 
            /home/rhos-ci/jenkins/workspace/DFG-storage-cinder-20_director-rhel-virthost-3cont_2comp-ipv4-vxlan-netapp-nfs-external-ssbarnea
            With the mention that limiting the job name is impossible, there are tens of people creating jobs and no way to enforce a limit, in addition that an attempt to rename >1000 existing jobs would be an epic failure.

            The only thing where it may be possible to cut few characters is on jenkins slave HOME directory and subfolder, but other than this nope. Even so, changing this would be quite complex too as it would  involve lots of slaves type which are created by various people where almost for sure you will endup with some not using the shortened home directory workaround.

            Still, even if I manage to pick the minimum possible home directory, of "/j" it will clearly not be enough to make virtuaenvs working because job names will continue to be too long. ** 

            Show
            ssbarnea Sorin Sbarnea added a comment - Any change of having this fixed, ever, at least for normal pipelines ? Here is one real life example:  /home/rhos-ci/jenkins/workspace/DFG-storage-cinder-20_director-rhel-virthost-3cont_2comp-ipv4-vxlan-netapp-nfs-external-ssbarnea With the mention that limiting the job name is impossible, there are tens of people creating jobs and no way to enforce a limit, in addition that an attempt to rename >1000 existing jobs would be an epic failure. The only thing where it may be possible to cut few characters is on jenkins slave HOME directory and subfolder, but other than this nope. Even so, changing this would be quite complex too as it would  involve lots of slaves type which are created by various people where almost for sure you will endup with some not using the shortened home directory workaround. Still, even if I manage to pick the minimum possible home directory, of " /j" it will clearly not be enough to make virtuaenvs working because job names will continue to be too long. ** 
            Hide
            olivergondza Oliver Gondža added a comment -

            I am unassuming as I do not intend to work on this anytime soon...

            Show
            olivergondza Oliver Gondža added a comment - I am unassuming as I do not intend to work on this anytime soon...
            Hide
            jglick Jesse Glick added a comment -

            Any change of having this fixed, ever

            Via my proposal in JENKINS-2111, perhaps.

            Show
            jglick Jesse Glick added a comment - Any change of having this fixed, ever Via my proposal in JENKINS-2111 , perhaps.
            Hide
            sflobbe Sander Flobbe added a comment -

            The description assumes "4096 is the maximal path allowed on linux". However the actual limit in some cases is much (!!) smaller. As mentioned in an earlier post by Sorin Sbarnea, with a python virtualenv command you will get shebang lines that include the full path. For example my bin/pip script created by virtualenv has this shebang line:

            #!/usr/share/tomcat/.jenkins/workspace/Waterworks_master-IAYUAOZ7D4F2MCG5DIMHAV3ODEQZACDRSHT3HA6N5UIRQXOCQQIQ/virtualenv/bin/python

            This results in an error in my Multibranch Pipeline job:

            /usr/share/tomcat/.jenkins/workspace/Waterworks_master-IAYUAOZ7D4F2MCG5DIMHAV3: bad interpreter: No such file or directory

            The actual cut-off point appears to be at character 80. This is on a Centos 7.5 system. Although external documentation suggests 127 as the limit with linux (and I don't understand why I am hitting a barrier at 80), both these numbers are way smaller than the implied and assumed 4096 limit in the description of this issue.

            Show
            sflobbe Sander Flobbe added a comment - The description assumes "4096 is the maximal path allowed on linux". However the actual limit in some cases is much (!!) smaller. As mentioned in an earlier post by Sorin Sbarnea , with a python virtualenv command you will get shebang lines that include the full path. For example my bin/pip script created by virtualenv has this shebang line: #!/usr/share/tomcat/.jenkins/workspace/Waterworks_master-IAYUAOZ7D4F2MCG5DIMHAV3ODEQZACDRSHT3HA6N5UIRQXOCQQIQ/virtualenv/bin/python This results in an error in my Multibranch Pipeline job: /usr/share/tomcat/.jenkins/workspace/Waterworks_master-IAYUAOZ7D4F2MCG5DIMHAV3: bad interpreter: No such file or directory The actual cut-off point appears to be at character 80. This is on a Centos 7.5 system. Although external documentation suggests 127 as the limit with linux (and I don't understand why I am hitting a barrier at 80), both these numbers are way smaller than the implied and  assumed 4096 limit in the description of this issue.
            Hide
            jglick Jesse Glick added a comment -

            My proposed patch in JENKINS-2111 fixes or at least greatly improves these issues.

            Show
            jglick Jesse Glick added a comment - My proposed patch in JENKINS-2111 fixes or at least greatly improves these issues.

              People

              • Assignee:
                Unassigned
                Reporter:
                olivergondza Oliver Gondža
              • Votes:
                2 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated: