[JIRA] (JENKINS-30148) Allocate shorter workspace if it will be too long for reasonable use inside build
Title: Message Title Jesse Glick commented on JENKINS-30148 Re: Allocate shorter workspace if it will be too long for reasonable use inside build My proposed patch in JENKINS-2111 fixes or at least greatly improves these issues. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30148) Allocate shorter workspace if it will be too long for reasonable use inside build
Title: Message Title Sander Flobbe commented on JENKINS-30148 Re: Allocate shorter workspace if it will be too long for reasonable use inside build 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. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30148) Allocate shorter workspace if it will be too long for reasonable use inside build
Title: Message Title Jesse Glick commented on JENKINS-30148 Re: Allocate shorter workspace if it will be too long for reasonable use inside build Any change of having this fixed, ever Via my proposal in JENKINS-2111, perhaps. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30148) Allocate shorter workspace if it will be too long for reasonable use inside build
Title: Message Title Oliver Gondža assigned an issue to Unassigned Jenkins / JENKINS-30148 Allocate shorter workspace if it will be too long for reasonable use inside build Change By: Oliver Gondža Assignee: Oliver Gondža Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30148) Allocate shorter workspace if it will be too long for reasonable use inside build
Title: Message Title Oliver Gondža commented on JENKINS-30148 Re: Allocate shorter workspace if it will be too long for reasonable use inside build I am unassuming as I do not intend to work on this anytime soon... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30148) Allocate shorter workspace if it will be too long for reasonable use inside build
Title: Message Title Sorin Sbarnea commented on JENKINS-30148 Re: Allocate shorter workspace if it will be too long for reasonable use inside build 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. ** Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.