[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Jesse Glick resolved as Won't Fix Suemiao Rossignol please do not reopen. If necessary, file a separate (but linked) bug report with complete steps to reproduce from scratch as well as FINE logs from jenkins.branch.WorkspaceLocatorImpl. Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline Change By: Jesse Glick Status: Reopened Resolved Resolution: Won't Fix 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Suemiao Rossignol reopened an issue Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline Change By: Suemiao Rossignol Resolution: Won't Fix Status: Resolved Reopened 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Suemiao Rossignol edited a comment on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I am using Jenkins 2.150.2 version but still hitting this issue?I also install short workspace pluginswithout plugins without any luck.Is this truly fixed? 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Suemiao Rossignol commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I am using Jenkins 2.150.2 version but still hitting this issue? I also install short workspace pluginswithout any luck. Is this truly fixed? 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Jesse Glick resolved as Won't Fix This issue became obsolete with the release of the fix of JENKINS-2111. Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline Change By: Jesse Glick Status: Reopened Resolved Resolution: Won't Fix 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline Change By: Vivek Pandey Labels: pipeline triaged-2018-11 workspace 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
sascha bates commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
My workaround for this was to define a jobName and then use the jobName in the workspace. The jobName var was also to account for feature branches and builds around several different microservices that might also have the same Jira id attached to them. Our feature branch work is all short lived and named feature/jira-12345-some-description. Our services are named my-service-name. The below lines result in a 'my-service-name-jira-12345' workspace name. 99% of the time we don't need to look at workspaces anyway, but this makes the console log readable as well as making it possible to write directory cleanup patterns based on naming. def jobName = JOB_NAME.replaceAll(/\/\w+%2F/,'-').toLowerCase() ansiColor( 'xterm' ) { timestamps {try {node() { ws( "workspace/${jobName}" ) { stage( 'Pull Github Repository' ) {
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title kpop edited a comment on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Removing the 'garbage' at the end causes name clashes (cf. JENKINS- 54540 54640 ). (edit: fixed issue link) 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title kpop commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Øyvind R, I agree: less is certainly better, but name clashes should be avoided. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Øyvind R commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline kpop, there is no way you need over 50 base-64 characters to avoid name clashes. Git manages with just 7 hex-characters for thousands of commits. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title kpop commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Removing the 'garbage' at the end causes name clashes (cf. JENKINS-54540). 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Tommy McNeely commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline WORKAROUND For users using python virtualenv, try using virtualenv --relocatable venv ... BEFORE calling "pip" That changes the shebang line to: #!/usr/bin/env python27 ... or whatever version of python you are using, but significantly shorter. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Jesse Glick commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Sorry, that was a corollary that should have been made explicit: if you are maintaining a persistent mapping of this kind, then the need to include some manner of hash in the workspace path disappears. (You would still need to translate dangerous characters to something more neutral like _.) 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Josh Trow commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I did read what you wrote, hence my question - nothing in this: Each node (master, agent) should just pay attention to when a workspace is used. (If in core, via WorkspaceList; otherwise, perhaps via WorkspaceListener.) Then record a workspaces.xml, a sibling of workspace/, with a list of records: relative workspace path, Item.fullName, timestamp. seems to say that you are intending to 'clean' or 'modify' or 'change' the paths from what they are today to anything nicer - just that you want to maintain a map of job to workspace for cleanup purposes down the road. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Jesse Glick commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline in that corresponding XML file you're holding a mapping of what the paths are today to some shorter friendly your name This. Read what I wrote. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Josh Trow commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Unless in that corresponding XML file you're holding a mapping of what the paths are today to some shorter friendly your name that is then used in actuality I'm still not sure how that resolves the issue of the workspace having a path that has a 'mangled' name. I agree that having better logic around work spaces and the ability to clean them up automatically is a good thing but I don't think it's directly related to this nor will one automatically solve the other (depending on the implementation it could) 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Jesse Glick commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline This is just beating around the bush. See JENKINS-2111 for the proper permanent solution to handling inelastic (“dumb”) build agents. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Aaron Marasco commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Stephen Connolly I didn't see anything in that PR addressing a possible leading "-" - are you assuming the path length should fix "most" cases? That's the problem I had as well as others previously (e.g. Alp Dener). Otherwise, kudos and thanks! 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Stephen Connolly edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
I'm adding some tweaks to the implementation in a [PR|https://github.com/jenkinsci/branch-api-plugin/pull/128].* Each agent's system properties will also be checked for a local override of path max. This will allow windows agents to have a shorter path max without affecting *nix agents* I am adding a second implementation that uses the [{{NameMangler}}|https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/NameMangler.java]. As {{NameMangler}} should always produce a safe name for all OSes (but it might be too long on windows if your SCM checkout is too deep... nothing we can do there) it is a simple boolean flag to enable/disable. And as it is opinionated it can only be set globally. System property will be {{jenkins.branch.WorkspaceLocatorV2Impl .ENABLE }} I suspect that the {{NameMangler}} version is the one people actually want, so before I default it on I would appreciate some real world feed-back
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Stephen Connolly commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I'm adding some tweaks to the implementation in a PR. Each agent's system properties will also be checked for a local override of path max. This will allow windows agents to have a shorter path max without affecting *nix agents I am adding a second implementation that uses the NameMangler. As NameMangler should always produce a safe name for all OSes (but it might be too long on windows if your SCM checkout is too deep... nothing we can do there) it is a simple boolean flag to enable/disable. And as it is opinionated it can only be set globally. System property will be jenkins.branch.WorkspaceLocatorV2Impl I suspect that the NameMangler version is the one people actually want, so before I default it on I would appreciate some real world feed-back 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Aaron Marasco edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
We just ran into a problem where the name of our git branch is "feature \ - \ -XXX" and Jenkins decided the name was too long, so stripped feature. Leaving a directory that starts with " \ - \ -". {code}13:22:18 [CentOS 6: Main RPM Build] Found files starting with hyphen13:22:18 [CentOS 6: Main RPM Build] error: Bad exit status from /var/tmp/rpm-tmp.mTAEkR (%install) {code}
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Aaron Marasco commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline We just ran into a problem where the name of our git branch is "feature-XXX" and Jenkins decided the name was too long, so stripped feature. Leaving a directory that starts with "-". 13:22:18 [CentOS 6: Main RPM Build] Found files starting with hyphen 13:22:18 [CentOS 6: Main RPM Build] error: Bad exit status from /var/tmp/rpm-tmp.mTAEkR (%install) 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Jesse Glick commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Yes the current behavior is intentional. Certainly it has some problems that affect some people; the previous behavior also had serious problems that affected lots of people. Rather than applying further tweaks, the basic assumption—that a workspace path on an agent (relative to the agent’s “filesystem root”) must be a function of the job’s full name so that it is guaranteed to be unique—should be discarded, in favor of a system of allocating short, legible workspace paths per job × agent and explicitly tracking them. This could be integrated with proper workspace cleanup (for “permanent, as opposed to elastic, agents), which Jenkins has never done, which is why I proposed such a rewrite in JENKINS-2111. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Oleg Nenashev commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Sam Van Oort Andrew Bayer rsandell Hi. Is it in the scope for the Pipeline team? Øyvind R has recently raised JENKINS-52911 to get some attention to it 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Jerome Mohanan commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Cant use the workaround in my case. I don't use docker, I build directly on a build server VM (Windows) agent{ node{ label 'my-node-label' customWorkspace "MyFixedLocation/MyPipelineName_${BRANCH_NAME}" } } In my case, I can't specify label field, so not possible to specify customWorkspace. Any other workarounds please.
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Jerome Mohanan edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Cant use the workaround in my case. I don't use docker, I build directly on a build server VM (Windows) {code:java} agent \ { node \ {label 'my-node-label'customWorkspace "MyFixedLocation/MyPipelineName_$ \ {BRANCH_NAME}" }} {code} In my case, I can't specify label field, so not possible to specify customWorkspace. Any other workarounds please.
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Jerome Mohanan updated an issue Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline Change By: Jerome Mohanan Priority: Critical Blocker 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Zangdaarr Mortpartout commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline We are using custom workspace but this is causing trouble with third party tools which do not know that custom workspaces exists. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Adam Daughterson commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline An acceptable workaround would be a flag to opt out of the workspace name mangling in either the Jenkinsfile or the multibranch configuration. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Adam Daughterson edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
After upgrade to this crufty new version of pipeline, all multibranch pipelines using older (eg no declarative pipeline stuffs like pipeline\{} agent\{} etc) syntax have now a useless name for the git repo, and first part of the name is truncated instead of the ending. Setting jenkins.branch.WorkspaceLocatorImpl.PATH_MAX=0 has no noticeable effect. Combining new and old syntax does not appear to get beyond carving a workspace, and attempting to set workspace via customWorkspace doesn't work at all.Who approved this disruptive myopic change? Way to break everything...
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Adam Daughterson commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
After upgrade to this crufty new version of pipeline, all multibranch pipelines using older (eg no declarative pipeline stuffs like pipeline{} agent{} etc) syntax have now a useless name for the git repo, and first part of the name is truncated instead of the ending. Setting jenkins.branch.WorkspaceLocatorImpl.PATH_MAX=0 has no noticeable effect. Combining new and syntax does not appear to get beyond carving a workspace, and attempting to set workspace via customWorkspace doesn't work at all. Who approved this disruptive myopic change? Way to break everything...
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Jakub Pawlinski commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Using
customWorkspace "${JENKINS_HOME}/Workspace/${URLDecoder.decode(JOB_NAME)}/${BUILD_NUMBER}"
Due to this change got some issues with c++ msbuild prebuild triggered scripts but managed to fix those
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Danny Tamsen commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Dalmo Santos _> Another possible solution is to utilize the 'customWorkspace' element as mentioned earlier. It would look something like:
agent{
node{
label 'my-node-label'
customWorkspace "MyFixedLocation/MyPipelineName_${BRANCH_NAME}"
}
}
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Dalmo Santos edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Hi!I found a palliative solution to the problem. I added the Allocate Workspace. It works on multibranch pipeline, on any node. Ex.:def wsDir = "/some/path/$ \ {env.BRANCH_NAME}"ws (wsDir) \ {// some block}
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Dalmo Santos commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Hi! I found a palliative solution to the problem. I added the Allocate Workspace. Ex.: def wsDir = "/some/path/$ {env.BRANCH_NAME} " ws (wsDir) { // some block }
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title jaeyun jeong commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Why is this hash code behind the folder name? is that collision between branches? So, Why does not jenkins.branch.WorkspaceLocatorImpl.PATH_MAX=0 have any problems? Please let me know 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Martin Häcker commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline On Linux this also creates the problem that shebangs that then include this path get too long and thus scripts (e.g. in python virtualenvs in that build location) cannot be executed. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Aurélien Bertron commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline David Wagner, how is your problem related to this bug? If it is not please open another ticket. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title David Wagner commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I got here because I would like to have two different multibranch pipeline jobs share the same workspace for a same branch. If I call ws(env.BRANCH_NAME) in both of my Jenkinsfile, it does the trick but when the branch is deleted, the multibranch pipeline scan will only delete the default workspace and not the custom workspace leaving the sources and the build artifacts on the node. Most other job types have a customWorkspace api that let the user define what the workspace should be. i understand that it can't be that simple for a multi-branch pipeline but maybe a custom workspace name template would work. 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title nicolas mettais commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Hi, when activating -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=0 (running on Windows platform), I get 3 folders created for every branch: projectname_branchname-C5MAL5QJSBT3VC7KWLCI3CTGCJVURIOQAGAQA2TXJGASFJP5755A projectname_branchname-C5MAL5QJSBT3VC7KWLCI3CTGCJVURIOQAGAQA2TXJGASFJP5755A@script projectname_branchname-C5MAL5QJSBT3VC7KWLCI3CTGCJVURIOQAGAQA2TXJGASFJP5755A@tmp when Jenkins pipeline is running Jenkinsfile, shell scripts are executed in the 1st one which is empty, while the code has been checked out in the one ending with @script Is this a side effect of this or related to another defect ? Thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title David Beck edited a comment on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline MSBuild does not support long file path names FYI Git does support long file paths but will break powershell and other command unless you sue use the //? access paths which almost no one does normally.This i a feature breaking bug that should be fixed sooner than later. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Greg Smith commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Also, I can confirm that msbuild does not work with long file names, even in those versions of Windows 10 where it has been enabled at the filesystem level. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Greg Smith commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I do understand why people are upset by this change. However, if you want the original behavior, you can set the below as an option on your jenkins java vm setup (for example, in /etc/default/jenkins) -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=0 Setting this back to the original behavior has generally satisfied us: I hope this option is not removed. But for those which this changed caused a problem, the above is a pretty OK solution (IMO) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Alexander Siniouguine commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline The only fix I found is to revert multibranch and related plugins to the version before september updates. This is a must fix for build to work in windows environments as well compatibility with previous builds. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title David Beck commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline MSBuild does not support long file path names FYI Git does support long file paths but will break powershell and other command unless you sue the //? access paths which almost no one does normally. This i a feature breaking bug that should be fixed sooner than later. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Greg Smith commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Those following this issue might try to enable the new long file name support in Windows 10 Anniversary Edition, where Microsoft has now removed the path limitation if you turn that support on. I ran into a very interesting problem with that setting enabled / on that new version of Windows: JENKINS-39179 Thought I would link here, in case anyone tries to go that route. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Alexander Siniouguine commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline This is a terrible issue and broke our builds completely on install. Can we have our paths back? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Martin Karing commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
This issue causes major problems in my msbuild projekts on windows. When using some NuGET dependencies you are practically guaranteed to exceed the path length limit due to these strange strings at the end of the directory names. I am using the safeNode implementation of Edward Easton. Here is a mostly platform independent implementation: {{import java.util.regex.Pattern def call(String label = null, Closure body) { node(label) { String path = pwd() String branchName = env.BRANCH_NAME if (branchName) { path = path.split(Pattern.quote(File.separator)) def workspaceRoot = path[0..<-1].join(File.separator) def currentWs = path[-1] // Here is where we make branch names safe for directories - // the most common bad character is '/' in 'feature/add_widget' // which gets replaced with '%2f', so JOB_NAME will be // ${PR}}OJECT_NAME}%2f$ {BRANCH_NAME} String newWorkspace = env.JOB_NAME.replace('/', '-') newWorkspace = newWorkspace.replace(File.separator, '-') newWorkspace = newWorkspace.replace('%2f', '-') newWorkspace = newWorkspace.replace('%2F', '-') // Add on the '@n' suffix if it was there if (currentWs =~ '@') { newWorkspace = "$ {newWorkspace}@${currentWs.split('@')[-1]}" } path = "${workspaceRoot}${File.separator}${newWorkspace} " } ws(path) { body() } } }}}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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 je
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Martin Karing edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
This issue causes major problems in my msbuild projekts on windows. When using some NuGET dependencies you are practically guaranteed to exceed the path length limit due to these strange strings at the end of the directory names.I am using the {{safeNode}} implementation of [~eeaston].Here is a mostly platform independent implementation: { { noformat} import java.util.regex.Patterndef call(String label = null, Closure body) {node(label) {String path = pwd()String branchName = env.BRANCH_NAMEif (branchName) {path = path.split(Pattern.quote(File.separator))def workspaceRoot = path[0..<-1].join(File.separator)def currentWs = path[-1]// Here is where we make branch names safe for directories -// the most common bad character is '/' in 'feature/add_widget'// which gets replaced with '%2f', so JOB_NAME will be// ${PR}}OJECT_NAME}%2f${BRANCH_NAME}String newWorkspace = env.JOB_NAME.replace('/', '-')newWorkspace = newWorkspace.replace(File.separator, '-')newWorkspace = newWorkspace.replace('%2f', '-')newWorkspace = newWorkspace.replace('%2F', '-')// Add on the '@n' suffix if it was thereif (currentWs =~ '@') {newWorkspace = "${newWorkspace}@${currentWs.split('@')[-1]}"}path = "${workspaceRoot}${File.separator}${newWorkspace}"}ws(path) {body()}}} {noformat } }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Gerbrand Stap commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
There seems to be another issue introduced with this update. Multi branch pipeline now ignores the workspace setting. We have the workspace on a separate drive, but all of a sudden Jenkins creates the workspace in the install directory. This still works correctly for single pipeline projects. Jenkins is running on Windows Server 2012 R2. Workspaces are created in "C:\Program Files (x86)\Jenkins\workspace". [Manage Jenkins -> Configure System -> Advanced... -> Workspace Root Directory] is set to "D:\workspace\$ {ITEM_FULL_NAME} "
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Tobias Pongs commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
I also have been having this issue. My workaround is to set the workspace with "ws('D:\...')". Additionally it seems that the workspace directory of the global settings is not considered. In my global setting I have specified a path like "D:\jenkins\workspaces", but the multibranch pipeline always creates a path under "C:\jenkins\workspace". With the workaround I could change the path for the job, but not for the script itself.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title David Beck commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I also have been having this issue. But I have just setup Jenkins to automate a MSBuild for our team. Pipeline jobs work fine but Multipath does not work. Currently our deepest file on our repository is 197 characters deep. leaving me just 63 for the file path. 52 are consumed by the supposed fix for %2 and that leaves me 11 chars C:\ consumes 3\ and then I can't handle even the git branch name. So this totally breaks my code. I know I am running close to the edge and will have a conversation with my devs about it but currently its a waste of 52 chars. I think I could live with 8 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Edward Easton commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Interestingly, this problem has come up before and been the subject of a plugin specifically for it: https://wiki.jenkins-ci.org/display/JENKINS/Short+Workspace+Path+Plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Christian Höltje commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
NO! I don't want to git clone 700MB repositories for twice for every build! I also need to compile code on multiple slaves, then copy stuff around to other slaves and then package stuff up in installers. Local workspaces must not be modified in between.
I totally agree that there needs to be a solution for things like 2.7gb git repositories (we have some) and lots of downloaded dependencies. I'm just saying that the default node() behavior isn't the right place to handle this. I would assume that anyone who needs that ability would use something like the external workspace plugin to do sane caching of data or using something like node('restriction') and ws() to ensure they don't keep getting new (empty) workspaces. With the current model, if you have 10 slaves, each with 4 executors, you have the possibility of needing to clone that repository up to 40 times, with a minimum of 10 (one per slave) per node() invocation.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Edward Easton commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Hi all, here's a workaround I use for this issue on Linux. I have this in a CPSWorkFlowLib var, lets call it 'safeNode.groovy':
def call(label=null, Closure body) {
node(label) {
def path = pwd()
def branchName = env.BRANCH_NAME
if (branchName) {
path = path.split('/')
def workspaceRoot = path[0..<-1].join('/')
def currentWs = path[-1]
// Here is where we make branch names safe for directories -
// the most common bad character is '/' in 'feature/add_widget'
// which gets replaced with '%2f', so JOB_NAME will be
// ${PROJECT_NAME}%2f${BRANCH_NAME}
def newWorkspace = env.JOB_NAME.replace('/','-')
newWorkspace = newWorkspace.replace('%2f', '-')
newWorkspace = newWorkspace.replace('%2F', '-')
// Add on the '@n' suffix if it was there
if (currentWs =~ '@') {
newWorkspace = "${newWorkspace}@${currentWs.split('@')[-1]}"
}
path = "${workspaceRoot}/${newWorkspace}"
}
ws(path) {
body()
}
}
Now in your pipeline code you can use it like:
safeNode {
sh "pip install pytest"
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Christoph Obexer commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I feel like the default workspace for node() should be special and should be removed as soon as the build is finished (or shortly after). NO! I don't want to git clone 700MB repositories for twice for every build! I also need to compile code on multiple slaves, then copy stuff around to other slaves and then package stuff up in installers. Local workspaces must not be modified in between. I'm pretty sure most git users would be upset about having to clone the repository for every build. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Tyrel Haveman updated an issue Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline After seeing the effects this can cause I'm changing it to Critical. It's almost a blocker... Change By: Tyrel Haveman Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Ruud van Asseldonk commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I upgraded Jenkins from 2.22 to 2.24 today, and I simultaneously updated all plugins. After that we started seeing this issue, and it is causing all of our Python builds to fail. The issue is that Pip inside a virtualenv cannot handle long path names, because it is based on a script that uses a shebang. The length of a shebang is hard-coded in the kernel to 128 characters, which was not long enough for the workspaces that Jenkins now generates. See also https://github.com/pypa/pip/issues/1773. To try and mitigate the problem I downgraded Jenkins to 2.22 and the multibranch plugin to 2.8. This did not resolve the issue. (After downgrading more plugins, I ended up in a state of incompatible plugins, which caused the organization (of the GitHub plugin) with all repositories and branches to become corrupt in Jenkins. I had to add a new organisation which caused a rebuild of all branches of all repositories, and which reset all branch numbers. Fortunately we were using Jenkinsfiles so at least the build configuration was preserved.) At this point I still haven’t been able to revert back to our old configuration, but at least there exists a workaround for the Python/Pip issue: instead of invoking virtualenv/bin/pip, invoke virtualenv/bin/python -m pip. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-i
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Christian Höltje commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I feel like the default workspace for node() should be special and should be removed as soon as the build is finished (or shortly after). If ws() is specified then it should follow the old-style workspace rules. Otherwise the maintenance becomes hard for the various slaves, unless you're recycling them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Christian Höltje commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Just trying to collect the problems as I see it: The path names are nearly useless for "humans". I'm not too upset about that on its own, since ideally Jenkins would manage everything in a smart way on its own. The path names may start with - which is a problem for various reasons. The path names are very long and may cause issues with Windows and even Linux. A lot of the old workspace cleanup methodologies no longer work (e.g. by matching the path with the job name). There are lots of shell and groovy scripts that try to check if a workspace could possibly be in use anymore and remove it if the job doesn't exist. This was already broken in pipeline builds, but it is much more obvious now. Forcing users (e.g. Jenkinsfile authors) to manage their workspace by hand seems wrong; they shouldn't be forced to use ws() and even forcing them to use deleteDir() makes me uncomfortable. node() doesn't have the same sticky properties as a regular build. So now you'll see every job on every slave because it is random. It feels like workspaces should overall be smarter... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Christian Höltje commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Another issue are directory names that start with -. It makes using commands more difficult (e.g. du -sch * needs to be du -sch – *). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Edward Easton commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Hi, This change was very bad for all Python development. Super-long shebang paths like this cause all standard Python entry points in virtualenv to fail due to the Linux operating system shebang length. This includes 'pip' and 'easy_install' ! I appreciate fixing the '%2f' was needed, but this is not the best way to do it I think. It's taken days and days fixing every single call to a subprocess with the standard workaround for this which is to run the programs as 'venv/bin/python venv/bin/entrypoint '. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Edward Easton updated an issue Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline Change By: Edward Easton Environment: Windows 2012 x64, Java 1.8, Jenkins 2.7.4, Pipeline: Multibranch 2.9, Pipeline: API 2.4 , Linux Python Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Christoph Obexer edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
I vote for an option like with Matrix projects "Use custom child workspace". If multibranch projects had such an option it could be used to solve this issue and the feature branch disk space problem at the same time.The default value could be {{ "${PROJECT_NAME}/${BRANCH_NAME}" }} and people with / in their branch names would simply get subdirectories (probably called features or releases) no one would get %2F in their folder names. Those with larger workspaces could set it to {{ "${PROJECT_NAME}" }} and enjoy saving lots of gigabytes of disk space.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Christoph Obexer edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
I vote for an option like with Matrix projects "Use custom child workspace". If multibranch projects had such an option it could be used to solve this issue and the feature branch disk space problem at the same time.The default value could be ``` {{ "${PROJECT_NAME}/${BRANCH_NAME}" ``` }} and people with / in their branch names would simply get subdirectories (probably called features or releases) no one would get %2F in their folder names. Those with larger workspaces could set it to ``` {{ "${PROJECT_NAME}" ``` }} and enjoy saving lots of gigabytes of disk space.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Christoph Obexer edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
I vote for an option like with Matrix projects "Use custom child workspace". If multibranch projects had such an option it could be used to solve this issue and the feature branch disk space problem at the same time.The default value could be ``` "${PROJECT_NAME}/${BRANCH_NAME}" ``` and people with / in their branch names would simply get subdirectories (probably called features or releases) no one would get %2F in their folder names. Those with larger workspaces could set it to ``` "${PROJECT_NAME}" ``` and enjoy saving lots of gigabytes of disk space.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Christoph Obexer commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
I vote for an option like with Matrix projects "Use custom child workspace". If multibranch projects had such an option it could be used to solve this issue and the feature branch disk space problem at the same time. The default value could be "$ {PROJECT_NAME}/${BRANCH_NAME}" and people with / in their branch names would simply get subdirectories (probably called features or releases) no one would get %2F in their folder names. Those with larger workspaces could set it to "${PROJECT_NAME} " and enjoy saving lots of gigabytes of disk space.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Tyrel Haveman edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Indeed, this was done to fix JENKINS-30744. Encoding the name gets rid of {{%2F}} which was there before in place of {{/}} in a branch name. Personally For our organization, {{%2F}} wasn't causing any problems (Maven doesn't seem to care) and I prefer it to this crap messy situation .
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Tyrel Haveman commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline Indeed, this was done to fix JENKINS-30744. Encoding the name gets rid of %2F which was there before in place of / in a branch name. Personally %2F wasn't causing any problems and I prefer it to this crap. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Tyrel Haveman commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
I was looking a bit and Jenkins source trying to find out where this bug might be, and now I'm getting a terrible feeling that this might actually be intentional. Check out this chunk of a unit test in WorkflowBranchProjectFactoryTest.java:
story.j.assertLogContains("branch=dev/main", b1);
story.j.assertLogContains("workspace=dev_main-ZFNHWJSHKH4HUVOQUPOQV6WFX7XUPIKIAQAQ3DV7CCAGIXQW7YSA", b1);
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Greg Smith commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline I would even vote for raising this to severe. I don't know what is worse – giant long workspace names, or randomly removing characters from the workspace names. I did go through and try to downlevel all of the plugins I had just updated – the problem never went away (I did it one by one – unfortunately, I was a couple of weeks behind, so there were a lot of updates) I just reached a point where my Jenkins install wouldn't start (too many cross dependencies), and I had to move back up to latest to get it started again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Tyrel Haveman edited a comment on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
[~gregcovertsmith] Yeah, characters are being removed from the beginning of the name. It's not always just the first character, though; it seems to depend on the length of the build name. Longer names have more characters removed.We do have a workaround, but it's annoying: Inside the {{node}} element of our Jenkinsfile we wrap the entire build also with : { { code:java} ws("workspace/${env.JOB_NAME}") { // ... } {code } }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Tyrel Haveman commented on JENKINS-38706
Re: Workspace directory names mangled in multibranch pipeline
Greg Smith Yeah, characters are being removed from the beginning of the name. It's not always just the first character, though; it seems to depend on the length of the build name. Longer names have more characters removed. We do have a workaround, but it's annoying: Inside the node element of our Jenkinsfile we wrap the entire build also with {{ws("workspace/$ {env.JOB_NAME} ") { ... } }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Greg Smith commented on JENKINS-38706 Re: Workspace directory names mangled in multibranch pipeline This just happened to us as well. Not only are the names super long with that UUID like value on them, but the first character of the branch name is missing too. If you look at Tyrel's example, his directory name is "ine-job_my-branch" – that was probably supposed to be "line" or something else. We are also seeing the first character removed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Tyrel Haveman created an issue Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline Issue Type: Bug Assignee: Unassigned Components: workflow-multibranch-plugin Created: 2016/Oct/04 5:09 PM Environment: Windows 2012 x64, Java 1.8, Jenkins 2.7.4, Pipeline: Multibranch 2.9, Pipeline: API 2.4 Labels: workspace pipeline Priority: Major Reporter: Tyrel Haveman Apparently after a recent update of plugins, our Multibranch Pipeline jobs started putting their workspaces in mangled locations. They used to be, for example, in D:\jenkins\cm-jenkins-09\my-pipline-job\my-branch-name and now they're like D:\jenkins\cm-jenkins-09\ine-job_my-banch-name-5P5URKHPJXWGGVIWDQOJBB3N7RJECAQJGFTDCVOPY3PABO7LNTIQ There are several problems with this: They're difficult to read with all that garbage at the end, and the beginning of the name sometimes cut off They're not organized within the parent job like they used to be This is causing files within them to have extremely long paths such that Windows won't actually let us delete them (Jenkins, CMD, and Windows Explorer all fail to delete them) It looks like, at least sometimes, jobs are getting a brand new workspace each time they run, causing disk space usage to climb very quickly
[JIRA] (JENKINS-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title
Tyrel Haveman updated an issue
Jenkins / JENKINS-38706
Workspace directory names mangled in multibranch pipeline
Change By:
Tyrel Haveman
Apparently after a recent update of plugins, our Multibranch Pipeline jobs started putting their workspaces in mangled locations. They used to be, for example, in {{D:\jenkins\cm-jenkins-09\my-pipline-job\my-branch-name}} and now they're like {{D:\jenkins\cm-jenkins-09\ine-job_my-banch-name-5P5URKHPJXWGGVIWDQOJBB3N7RJECAQJGFTDCVOPY3PABO7LNTIQ}}There are several problems with this:# They're difficult to read with all that garbage at the end, and the beginning of the name sometimes cut off# They're not organized within the parent job like they used to be# This is causing files within them to have extremely long paths such that Windows won't actually let us delete them (Jenkins, CMD, and Windows Explorer all fail to delete them) # It looks like, at least sometimes, jobs are getting a brand new workspace each time they run, causing disk space usage to climb very quickly Let me know if I can provide any other information to help solve this. This is a private Jenkins install so I can't point you to it.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
