[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Maximilian Weig assigned an issue to Jesse Glick Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Maximilian Weig Assignee: A. Jesse Jiryu Davis Glick 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Maximilian Weig assigned an issue to A. Jesse Jiryu Davis Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Maximilian Weig Assignee: Maximilian Weig A. Jesse Jiryu Davis 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Maximilian Weig assigned an issue to Maximilian Weig Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Maximilian Weig Assignee: Jesse Glick Maximilian Weig 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. are you suggesting to use branch-api 2.0.21 ? When released. Or you can install a build from my PR today. What does it have different than 2.0.20 A completely different system for selecting and managing workspace paths. Best discussed in the other issue or PR. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick updated JENKINS-34564 Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Jesse Glick Status: Fixed but Unreleased Resolved 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Uma Shankar commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Jesse Glick Apologies for reopening this issue. Regarding proposed implementation in JENKINS-2111, are you suggesting to use branch-api 2.0.21 ? What does it have different than 2.0.20, would like to know before putting it on production Jenkins instance? Also, JENKINS-2111 looks more about cleanup than fixing multi branch workspace folder name. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick updated JENKINS-34564 Please do not reopen. If you encounter bugs, file them separately with complete steps to reproduce from scratch. Or just try my proposed implementation of JENKINS-2111, which reduces path lengths considerably. Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Jesse Glick Status: Reopened Fixed but Unreleased Resolution: 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Uma Shankar commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Hey guys, this seems to be still a problem with latest LTS Jenkins, I have Jenkins on Windows with a slave. I have used starting parameter as -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=2 works well on master, however builds on Node is still creating %2F folder which is breaking all the MSBuild projects Folder on Master: Folder on Slaves: Jenkins Version: Jenkins ver. 2.138.2 Branch API version: 2.0.20 Is there some specific configuration for slaves? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Uma Shankar edited a comment on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Hey guys, this seems to be still a problem with latest LTS Jenkins, I have Jenkins on Windows with a slave. I have used starting parameter as -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=2 works well on master, however builds on Node is still creating %2F folder which is breaking all the MSBuild projects Folder on Master:!image-2018-11-08-11-41-20-416.png|width=798,height=163! Folder on Slaves:!image-2018-11-08-11-41-54-437.png|width=785,height=184! Jenkins Version: [Jenkins ver. 2.138.2|https://jenkins.io/]Branch API version: [ 2.0.20 |https://jenkins.liveoptics-uat.com/pluginManager/plugin/branch-api/thirdPartyLicenses] Is there some specific configuration for slaves? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Uma Shankar reopened an issue Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Uma Shankar Resolution: Fixed 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Uma Shankar updated an issue Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Uma Shankar Attachment: image-2018-11-08-11-41-54-437.png 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Uma Shankar updated an issue Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Uma Shankar Attachment: image-2018-11-08-11-41-20-416.png 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Nick Jones commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Attempting to use '\\?\' as a path prefix – in my case, setting '\\?\C:\Jenkins' as the "Remote root directory" for my JNLP-connected Windows agent – resulted in a "java.nio.file.InvalidPathException: Illegal character [?] in path" exception being thrown, which similar to https://bugs.openjdk.java.net/browse/JDK-8165748 (although I'm using the Oracle JRE8). It would appear that my only options with Windows agents to reduce overall path length (until JENKINS-2111 is implemented) is the use of the '-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX' parameter, which given the merge of https://github.com/jenkinsci/branch-api-plugin/pull/62 would appear to support generated paths as short as 12 characters, far less than the 80 being generated by default. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title diewu qin commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Anyone can tell me if this issue fixed? I use parameter " -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=20 " but did not work, and my jenkins version is 2.89.4. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Michael Neale commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Thanks for the update. Yes makes sense. Early on the names of job and disk were the same (but that changed about 18 months ago, hence confusion!) 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jonas Hanschke resolved as Fixed Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Jonas Hanschke Status: Reopened Resolved Resolution: Fixed 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jonas Hanschke commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Michael Neale - sorry if I am totally off track here, but yeah, I though it was all about what is on disk. The very first comment to this issue, made by you , actually states this, if I don't get it all wrong: This also breaks tools like "npm run" as well (even on filesystems where it is ok). "%" is not recommended as a path name on any platform, even if it is tolerated in some cases. I think the %2F causes more problems that people realise, so picking something else would make more sense vs making it an "advanced" option. However, after reading that you and Robert Watkins state that you have no % character in your workspace paths, I started digging deeper. And it turns out that the problem was, that I (long time ago) had installed the "Short Workspace Path" plugin. I was this that controlled my path names. While keeping the paths very short indeed, it still kept the %2F in the name. I have now removed the plugin, and resorted to limiting path length through MAX_PATH=54. This works, and also eliminates the %2F, since it only includes the very last character of the branch name in the folder name. So, thank you for putting me on the right path to solve this long-term problem on our server! And apologies for incorrectly reopening this issue, I will close it now again. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Michael Neale commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. no idea what this ticket is now about The original "solution" proposed was to tweak how the generated "jobs" are named, but was it really about what is on disk? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Robert Watkins commented on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
The env.JOB_NAME still has escaped characters. Example usage in my pipelines:
def notifySuccessful() {
hipchatSend color: 'GREEN', credentialId: 'HipChat', message: "${env.JOB_NAME.replace('%2F', '/')} ${env.BRANCH_NAME} ${env.BUILD_NUMBER} Successful", notify: true, room: 'Build Server Messages', sendAs: 'Jenkins', server: '', v2enabled: false
}
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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Robert Watkins commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. The file system hasn't used % for some time (since Jesse's fixes in 2016) - but it also can't be mapped back to the branch name. The way I've been using to get the branch name (e.g. to publish artefacts to S3 in a branch-specific folder) is to use `env.BRANCH_NAME` This works for me - I don't really care where on disk my build is located, but I do care where I'm going to put it. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Michael Neale commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. I am pretty sure long ago the % was dropped from the file name on disk and another scheme was used (and then the other length problems result). I use git flow all the time and don’t see % on disk since over a year. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Varun Reddy commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Thanks Stephen Connolly yes that is exactly what I am trying to communicate. As there are two issues and only one is fixed(MAX PATH). This is a breaking change for users of git-flow and also who name the branch name contains / 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jonas Hanschke reopened an issue See my comment in the discussion Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Jonas Hanschke Resolution: Duplicate Status: Closed Reopened 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
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jonas Hanschke updated an issue Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Jonas Hanschke Comment: See my comment in the discussion 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jonas Hanschke commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Stephen Connolly - if you read the actual description of this issue (and large parts of the discussion) you will find that the actual issue has not been resolved: Replacing slashes from branch names with %2F causes lots of tools to not work within the jenkins workspace (see discussion above for examples Using a custom workspace in the pipeline script can be a workaround, but it has its limitations. For example, for us it breaks builds for pull requests with Bitbucket server. Slashes in branch names are very common since they are used in git flow, the most widespread branching concept in the git world, so this is not an obscure problem. Somehow, this issue's discussion at some point shifted the focus towards maximum workspace path length - which was indeed an issue as well, but a separate one. (Still, I am very thankful that you fixed that one!) I think this is what Varun Reddy is referring to and as you can see from many, many comments above, it is affecting the work of lots of people. Therefore I think this issue should be reopened. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Varun Reddy commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. After setting the PATH_MAX = 0 the issue with long path has been resolved. I am still having issues with / as my branch name is release/1.0.0. Is there a solution for this problem? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Stephen Connolly commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Sheamus Roche this all depends on your definition of fix. In Jenkins, job names cannot contain a / ever. In 2.0.8 (and some earlier versions), we ensure that the job names never contain a / by encoding the / as %2F which fixes the job name. There are also fixed any places where we found links to jobs that were not correctly encoding links to the job (as to work correctly the URL needs to be double encoded so you get %2F -> %252F (which the browsers "helpfully" display as %2F so you might not realise that the URL has been double-encoded) Now on-disk, there are different rules that govern the on-disk filename, so we instead apply an encoding to map job names into 32-char max names with only a safe character set used and when necessary a hash of the full name is used to abbreviate the job name to ensure it fits into 32-char max. Next there are issues with workspace paths for jobs, so there is another encoding of the job workspace (I'd like to switch that to use the same mapping as for the job name, but that is a different feature) this means that the job workspace on agents will be another name that is controlled by -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=... Finally the env.BRANCH_NAME should be the unescaped un-modified name of the branch. All the above is basically functioning as intended... so the question is "what was your 'issue' and - assuming it is the workspace path length one - did you change the system property and find your issue fixed?" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Sheamus Roche commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Hi Stephen Connolly, does 2.0.8 fix handling "/" in jenkins job name or not? I've just created my first multi-branch pipeline and coming across this issue in job generated from feature/development branch for the first time... 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Stephen Connolly commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Upgrade branch-api to 2.0.8 (which should work on any Jenkins from 1.642.3 upwards) 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title davida2009 commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Stephen Connolly Thanks, and please will you clarify how to get the change that you merged? Is it in Jenkins 2.50? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Stephen Connolly commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. To set it from start-up add a system property: -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=... To change it at run-time, in the groovy console run: jenkins.branch.WorkspaceLocatorImpl.PATH_MAX=... Try not to change it often as you will litter the old workspaces every time you change it 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title davida2009 commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Stephen Connolly How does one set PATH_MAX? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Stephen Connolly commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Jason MCDev did you try setting PATH_MAX (which was why this issue was marked as closed) : https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/WorkspaceLocatorImpl.java#L59 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jason MCDev commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. I was able to get the freestyle multi-branch project working with the Bitbucket plugin after upgrading Jenkins and going through upgrading every plugin involved. The long paths still cause issues on Windows. I had to upgrade my build agents to Windows Server 2016 and enable long paths. Some tools in the MS stack still have issues ( nuget restore ). This gets me closer, but I would really love to see a shorter path. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jason MCDev commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. I have tried the Bitbucket team/project and freestyle multi-branch project. This is what I have installed - I need to use Bitbucket and handle building feature branches. I didn't see a "Freestyle multibranch" plugin as listed as installed in the admin section. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jason MCDev updated an issue Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Jason MCDev Attachment: projectTypes.PNG 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Patrick Wolf commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Wait. Did you say you are hitting this on a Freestyle multibranch project, Jason MCDev? If that is true, that is an entirely different plugin. Multibranch freestyle jobs are implemented in this plugin: https://wiki.jenkins-ci.org/display/JENKINS/Multi-Branch+Project+Plugin 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jason MCDev commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. That's what I thought @Stephen Connolly. I have the following or (tried the following): Bitbucket Branch Source Plugin: 2.1.0 Branch API Plugin: 2.0.8 Multi-Branch Project Plugin: 0.6 Jenkins: 2.32.2 Thanks! 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Stephen Connolly commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. What plugin versions are you on Jason MCDev if you are on all the latest, you should not have this as a problem 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jason MCDev commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. There is so much info here. I am hitting the original encoding issue with a freestyle multibranch project using BitBucket project. We use Visual Studio, Nuget, msbuild which are all dying on the the %2n. What do I have to do to get around that encoding being used? Please help. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title John Smith commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Hi Tyrel Haveman, please see https://issues.jenkins-ci.org/browse/JENKINS-34564?focusedCommentId=281910=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-281910. You can try setting the "jenkins.branch.WorkspaceLocatorImpl.PATH_MAX" environment variable to the maximum length Jenkins should use for workspace paths. There are several ways you can set environment variables in Jenkins so I won't explain that here but Google should have instructions if you need assistance. Note that the release notes at https://wiki.jenkins-ci.org/display/JENKINS/Branch+API+Plugin probably need to be updated. Right now, the release notes for Version 1.11 still say "The default value is 80; values as low as 54 (but no lower) are possible". The release notes for Version 2.0.7 should probably say that the lower limit is now 12. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Tyrel Haveman commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Thank you for the link. That is very helpful. As far as I can see, it still doesn't answer some of davida2009's questions: Does it mean that the concerns about long path names are mitigated? Where would the user set the path length? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. https://wiki.jenkins-ci.org/display/JENKINS/Branch+API+Plugin is the wiki for the plugin named in this issue. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Tyrel Haveman commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. You are incredibly unhelpful Jesse Glick. Your comment does not summarize the state of this issue, it does not indicate whether this change is now in Jenkins, it does indicate that this mitigated, it does not tell the user how to set a path length. The changelog for workflow-api plugin, which I had to dig around for because you seem to be unable to link to, has not been updated since you checked in your changes. https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+API+Plugin – So it doesn't answer any of these questions either. Please just answer people's questions. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. See release notes for this 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title davida2009 commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Hi Stephen Please will you summarize the state of this issue? Does the merge of the pull request mean that this change is now in Jenkins? Does it mean that the concerns about long path names are mitigated? Where would the user set the path length? Sorry for the many questions but this issue spans lots of Jira issues and is hard to track by the uninformed. Thanks David 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Stephen Connolly closed an issue as Duplicate Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Stephen Connolly Status: Reopened Closed 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/branch/WorkspaceLocatorImpl.java src/test/java/jenkins/branch/WorkspaceLocatorImplTest.java http://jenkins-ci.org/commit/branch-api-plugin/6df91ed6911e49df85d3af2efd777ab330d5c497 Log: Merge pull request #62 from creste/jenkins-34564 JENKINS-34564 Allow workspace paths to be less than 54 characters. Compare: https://github.com/jenkinsci/branch-api-plugin/compare/e856fdf42eda...6df91ed6911e 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title John Smith commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. I submitted a Pull Request to reduce the minimum length of workspace directories from 54 characters to 12 characters when -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX is set to a value between 1 and 54. The pull request is at https://github.com/jenkinsci/branch-api-plugin/pull/62. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Hans Schulz commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. The change was introduced in version 1.11 of the Branch API Plugin (branch-api). 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Paul Kordes commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Yes, PLEASE! Which plugin and what version fixes this and where do you specify the change. I have a bunch of plugins that all refer to Pipeline and I don't see this option anywhere. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title davida2009 commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. I agree with Dmitriy Belyaev. It's very hard to find out what is going on with this issue. Also, I think that quite a while back there were comments that the issue shouldn't be fixed in the multibranch project plugin but in some other part of the system. It would be very helpful if this could all be clarified. Jesse mentioned: Current plugin releases fix the originally reported problem... Is he referring to the multibranch project 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Dmitriy Belyaev commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Jesse Glick As I mentioned in another issue, simple link can help a lot to people in order to find information about changes done or planned to be done. Currently I am just going trough an endless loop between dependent but 'Resolved as duplicate' issues trying to find the origin where the actual work is done. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Bruce Rust commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. 1. You mention the "customizable via system property" detailed in the release notes. But I cannot find those release notes anywhere. I think I found what I needed on a different but related issue that somebody commented on. Can you provide a link to the necessary information so I have the full listing of what is available and the release notes, etc.? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Current plugin releases fix the originally reported problem, that some characters are unsupported in workspace names. It also fixes the problem of workspace names of unbounded length, for example due to long branch names. The new bound is customizable via system property, and the new behavior can be turned off entirely via that same system property, as detailed in the release notes for this plugin. A more comprehensive solution that would satisfy a larger proportion of use cases out of the box needs to wait for an overhauled workspace handling system as described in JENKINS-2111. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title davida2009 commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. What is the current status of this issue please? I am still running plugin 'Multi-Branch Project Plugin' v.0.3 (the latest is 0.5.1) so that my msbuild jobs run correctly on Windows. I don't understand where the current fix is applied or whether I should wait for a new fix. Please will someone clarify the 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Marco Bachmann commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. but how would you do that in a multibranch scenario? Each mount must be dynamically created and unique based on the branch beeing built 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title James Dumay commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. In the past I've mounted subdirectories as virtual drives to get around windows 260 character paths. With some experimentation there could be decent workaround in it. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title James Dumay edited a comment on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. In the past I've [mounted subdirectories as virtual drives|http://superuser.com/questions/109407/how-do-you-mount-a-directory-as-a-drive-in-windows-7] to get around windows 260 character paths path limitations . With some experimentation there could be decent workaround in it. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Marco Bachmann commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. I'm also a bit disappointed. I have the workspace folder on C:\ and still can't install the nuget packages in the root of my repo since one nuget package has a long name. Using the long path trick on windows 10 isn't helping since the application that writes the files (in my case nuget) does not support it and throws errors. So no workaround possible for my situation. Is there any perspective on this? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Sorin Sbarnea commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. I was hit by this bug again and it really drives me insane. I find really disappointing to see how users feedback is dismissed with remarks that aim to imply that the problem is not caused by this plugin and that instead is floating around somewhere between linux kernel and other tools using virtual environments (virtualenv,...). The reality is that this change is causing outages to 90% of the users, we cannot rely on dirty hacks forever just because someone puts "safety" (huge hash) before system uptime or usability. Let's be a bit pragmatic here, let's fix something that is affecting 9/10 users of this plugin instead of trying to fix a non-problem: hash collisions (more likely to be hit by an asteroid than having someone using this approach to compromise your jenkins instance, they are tons other more accessible). Now let me go back to changing jenkins home directory and patching the config file 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Tyrel Haveman edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
Our workaround involves creating workspace paths based on the parent job and simplieifed simplified branch name, with a limit on length, and using a small hash if the length is too long.For example, in the job {{example-core-pipeline}}, we might have a branch named {{feature/adding-something-important}} ends up going into the path {{D:\jenkins\workspace\example-core-pipeline\adding-somB5}}, and a branch named {{feature/goodbye-bugs}} goes to {{D:\jenkins\workspace\example-core-pipeline\goodbye-bugs}}.Trimming off the branch prefix ({{feature/}} in these cases) helps to shorten the path somewhat. We chose to limit the rest of the branch name when used as a folder name to 12 characters. If it is longer, it gets trimmed to 10 characters and the rest of the name is hashed to a simple 2-character hash.We consider it extremely unlikely that we would have two branches with similar enough names that the first 10 characters plus a 2-character hash will create a collision. On our very active 18-member development team we've been using this since just after I reported JENKINS-38706 with high success. Through many dozens of branches there have been no collisions, the paths are human-readable, and they are not too long for our 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
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Tyrel Haveman commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Our workaround involves creating workspace paths based on the parent job and simplieifed branch name, with a limit on length, and using a small hash if the length is too long. For example, in the job example-core-pipeline, we might have a branch named feature/adding-something-important ends up going into the path D:\jenkins\workspace\example-core-pipeline\adding-somB5, and a branch named feature/goodbye-bugs goes to D:\jenkins\workspace\example-core-pipeline\goodbye-bugs. Trimming off the branch prefix (feature/ in these cases) helps to shorten the path somewhat. We chose to limit the rest of the branch name when used as a folder name to 12 characters. If it is longer, it gets trimmed to 10 characters and the rest of the name is hashed to a simple 2-character hash. We consider it extremely unlikely that we would have two branches with similar enough names that the first 10 characters plus a 2-character hash will create a collision. On our very active 18-member development team we've been using this since just after I reported JENKINS-38706 with high success. Through many dozens of branches there have been no collisions, the paths are human-readable, and they are not too long for our 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
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Code changed in jenkins User: Stephen Connolly Path: pom.xml http://jenkins-ci.org/commit/branch-api-plugin/dba46877d0c12703c8c812f769acc30d65030659 Log: Merge pull request #55 from jglick/compatibleSinceVersion JENKINS-34564 compatibleSinceVersion=1.11 (cherry picked from commit 035c7e29193bdefc16a569047661471a2249ad82) 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Code changed in jenkins User: Stephen Connolly Path: pom.xml http://jenkins-ci.org/commit/branch-api-plugin/035c7e29193bdefc16a569047661471a2249ad82 Log: Merge pull request #55 from jglick/compatibleSinceVersion JENKINS-34564 compatibleSinceVersion=1.11 Compare: https://github.com/jenkinsci/branch-api-plugin/compare/81e61a4cb5a7...035c7e29193b 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. it'll be half the length Base64 is only about 20% shorter than Base32 (you forgot the logarithm here). Anyway you'll have potential problems with case-insensitive file systems Right, it can result in collisions on Windows and Mac. You could just use a UUID. No, because these are not deterministic from the job. the one of getting checksum collisions The probability of checksum collisions is not my concern. It is malicious collisions, which are easily constructed with weakened hashes. Escape all underscores Still vulnerable to collisions. There are plenty of variants which are not, but these also expose builds to failures due to branch name length, which was also a reported problem—not just charset restrictions. The real fix is to maintain a per-node database of workspaces, as discussed in JENKINS-2111. Then each workspace can be given a guaranteed unique, human-readable name of guaranteed maximum length—as well as solving other longstanding issues not limited to branch projects. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Alastair D'Silva edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
The technique that I proposed when I added a configurable encoding to the branch names is as follows: { quote code:java } /** * Create a clean version of the name, suitable for use as file paths * @return the cleaned name */private String stripName() {String name = getName().replaceAll("_", "___"); // Escape all underscoresreturn Util.rawEncode(name).replaceAll("%2F", "_"). // Replace forward slash with underscorereplaceAll("%", "__"); // Replace remaining % with double underscore}{ quote code } This maintains a unique, human readable form that doesn't (typically) add many characters to the branch name. Perhaps we could go with something similar?
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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Alastair D'Silva edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
The technique that I proposed when I added a configurable encoding to the branch names is as follows: {{ /** * Create a clean version of the name, suitable for use as file paths * @return the cleaned name */private String stripName() {String name = getName().replaceAll("_", "___"); // Escape all underscoresreturn Util.rawEncode(name).replaceAll("%2F", "_"). // Replace forward slash with underscorereplaceAll("%", "__"); // Replace remaining % with double underscore} }} This maintains a unique, human readable form that doesn't (typically) add many characters to the branch name. Perhaps we could go with something similar?
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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Alastair D'Silva edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
The technique that I proposed when I added a configurable encoding to the branch names is as follows:{ { quote} /** * Create a clean version of the name, suitable for use as file paths * @return the cleaned name */private String stripName() {String name = getName().replaceAll("_", "___"); // Escape all underscoresreturn Util.rawEncode(name).replaceAll("%2F", "_"). // Replace forward slash with underscorereplaceAll("%", "__"); // Replace remaining % with double underscore} {quote } } This maintains a unique, human readable form that doesn't (typically) add many characters to the branch name. Perhaps we could go with something similar?
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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Alastair D'Silva commented on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
The technique that I proposed when I added a configurable encoding to the branch names is as follows: /**
Create a clean version of the name, suitable for use as file paths
@return the cleaned name */ private String stripName() { String name = getName().replaceAll("_", "___"); // Escape all underscores return Util.rawEncode(name). replaceAll("%2F", "_"). // Replace forward slash with underscore replaceAll("%", "__"); // Replace remaining % with double underscore }
This maintains a unique, human readable form that doesn't (typically) add many characters to the branch name. Perhaps we could go with something similar?
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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Sorin Sbarnea commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. I find ironic the fact that this fix that was supposed to help is creating more issues. Let's face it: the probability of causing build failures due to path limitations is 1000... times bigger than the one of getting checksum collisions. I have seen LOTS of build failing due to PATH length related issues (for both job and workspace) but never a checksum collision, even for very short ones. I am sure that someone with more time could compute the real probabilities 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Robert Watkins commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. You could just use a UUID. The canonical form is 36 characters long, and you can express one in Base32 in just 16 characters. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Robert Watkins edited a comment on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. bq. This is using SHA-256 encoded in Base32So optionally use SHA-256 encoded in [RFC-4648|https://en.wikipedia.org/wiki/Base64#RFC_4648]-flavoured Base64 - it'll be half the length. Hmm. No, you'll have potential problems with case-insensitive file systems. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Robert Watkins edited a comment on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. bq. This is using SHA-256 encoded in Base32So use SHA-256 encoded in [ RFC-4648 |https://en.wikipedia.org/wiki/Base64#RFC_4648] -flavoured Base64 - it'll be half the length. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Robert Watkins commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. This is using SHA-256 encoded in Base32 So use SHA-256 encoded in RFC-4648-flavoured Base64 - it'll be half the length. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. This is using SHA-256 encoded in Base32, it is different. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Gabriel Le Breton edited a comment on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Is the lenght length limit documented somewhere?There's usually no collision with git sha hash and it's 41 characters long. Jenkins seems to use a 53 character characters long hash . 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Gabriel Le Breton commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Is the lenght limit documented somewhere? There's usually no collision with git sha hash and it's 41 characters long. Jenkins seems to use a 53 character long. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Why cant the hash just be shortened? It is already as short as it can be while guaranteeing that there is no collision between jobs. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Ben Herfurth commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Why cant the hash just be shortened? It worked for all of us before the change. Now it does not work anymore ==> change it back please. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Michael Neale commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Yes as per: http://stackoverflow.com/questions/1880321/why-does-the-260-character-path-length-limit-exist-in-windows \\?\ is prefix to use. This seems to imply that on windows 10 you can just change the registry and you don't have to do anything else: http://betanews.com/2016/05/29/long-paths-windows-10/ 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. IIRC there is some trick to make Windows behave properly here: prepending \\?\ or the like to the agent FS root. In general we cannot protect you from the consequences of having deep workspace path hierarchies. The former behavior (using raw Item.fullName) was shorter in some cases, but also unbounded in length and so caused problems for people with, for example, long branch names; the current behavior at least guarantees a bound on the part Jenkins controls. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Michael Neale commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. perhaps its time to have a shorter hash-only thing to not eat the path length... (given many people are setting it to shorter and don't miss the 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Daniel Beck commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Jesse Glick 80 characters is not really that long It's a third of the total possible path length on Windows. Some "special" tools on Linux are also shitty about this. When I was running on Windows, I set the agent home to D:\J, and the hudson.model.Slave.workspaceRoot to ws, to waste as few chars as possible. This change would have wrecked my builds because Java devs routinely use up ~200 chars in deeply nested, verbosely named folder hierarchies. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Gabriel Le Breton edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I updated my plugins recently and my builds stopped working. I tried [Jesse Glick's suggestion|https://issues.jenkins-ci.org/browse/JENKINS-34564?focusedCommentId=272709=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272709] and it worked, but branches names are now stripped (I'm ok with that).For the record, in my case, it was failing to create install packages in a python * virtualenv inside working directory * (path too long), during {{pip install -r requirements.txt}}:{code}bad interpreter: Permission denied{code}Before plugin update {color:green}(was working, 56 characters){color}:{code}/var/lib/jenkins/workspace/project/project/master@script{code}After update {color:red}(failing, 109 characters){color}:{code}/var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E@script{code}Adding the following line to {{/etc/default/jenkins}}:{code}JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30"{code}Results in this {color:green}(working, 88 characters){color}:{code}/var/lib/jenkins/workspace/r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script{code}Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash.In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too:{quote}{{/j}} folder, as opposed to {{/var/lib/jenkins}}.{quote}But not quite sure what's the best way to achieve this.Related SO Questions:http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-buildhttp://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Gabriel Le Breton edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I updated my plugins recently and my builds stopped working. I tried [Jesse Glick's suggestion|https://issues.jenkins-ci.org/browse/JENKINS-34564?focusedCommentId=272709=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272709] and it worked, but branches names are now stripped (I'm ok with that). For the record, in my case, it was failing to create a python virtualenv inside working directory (path too long), during {{pip install -r requirements.txt}}:{code}bad interpreter: Permission denied{code} Before plugin update {color:green}(was working, 56 characters){color}:{code}/var/lib/jenkins/workspace/project/project/master@script{code}After update {color:red}(failing, 109 characters){color}:{code}/var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E@script{code}Adding the following line to {{/etc/default/jenkins}}:{code}JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30"{code}Results in this {color:green}(working, 88 characters){color}:{code}/var/lib/jenkins/workspace/r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script{code}Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash.In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too:{quote}{{/j}} folder, as opposed to {{/var/lib/jenkins}}.{quote}But not quite sure what's the best way to achieve this.Related SO Questions:http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-buildhttp://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Gabriel Le Breton edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I updated my plugins recently and my builds stopped working. I tried [Jesse Glick's suggestion|https://issues.jenkins-ci.org/browse/JENKINS-34564?focusedCommentId=272709=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272709] and it worked . Branches , but branches names are now stripped Instead (I'm ok with that) .Before plugin update {color:green}(was working, 56 characters){color}:{code}/var/lib/jenkins/workspace/project/project/master@script{code}After update {color:red}(failing, 109 characters){color}:{code}/var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E@script{code}Adding the following line to {{/etc/default/jenkins}}:{code}JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30"{code}Results in this {color:green}(working, 88 characters){color}:{code}/var/lib/jenkins/workspace/r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script{code}Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash.In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too:{quote}{{/j}} folder, as opposed to {{/var/lib/jenkins}}.{quote}But not quite sure what's the best way to achieve this.Related SO Questions:http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-buildhttp://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Gabriel Le Breton edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I updated my plugins recently and my builds stopped working. I tried [Jesse Glick's suggestion|https://issues.jenkins-ci.org/browse/JENKINS-34564?focusedCommentId=272709=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272709] and it worked. Branches names are now strippedInstead.Before plugin update {color:green} (was working , 56 characters ) {color} :{code}/var/lib/jenkins/workspace/project/project/ branch_name master @script{code}After update {color:red} (failing , 109 characters ) {color} :{code}/var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E@script{code}Adding the following line to {{/etc/default/jenkins}}:{code}JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30"{code}Results in this {color : green}(working, 88 characters){color}: {code}/var/lib/jenkins/workspace/r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script{code}Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash.In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too:{quote}{{/j}} folder, as opposed to {{/var/lib/jenkins}}.{quote}But not quite sure what's the best way to achieve this.Related SO Questions:http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-buildhttp://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Gabriel Le Breton edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I updated my plugins recently and my builds stopped working. I tried [Jesse Glick's suggestion|https://issues.jenkins-ci.org/browse/JENKINS-34564?focusedCommentId=272709=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272709] and it worked. Branches names are now strippedInstead.Before plugin update (was working):{code}/var/lib/jenkins/workspace/project/project/branch_name@script{code}After update (failing):{code}/var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E @script {code}Adding the following line to {{/etc/default/jenkins}}:{code}JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30"{code}Results in this:{code}/var/lib/jenkins/workspace/r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script{code}Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash.In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too:{quote}{{/j}} folder, as opposed to {{/var/lib/jenkins}}.{quote}But not quite sure what's the best way to achieve this.Related SO Questions:http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-buildhttp://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Gabriel Le Breton edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I updated my plugins recently and my builds stopped working. I tried [Jesse Glick's suggestion|https://issues.jenkins-ci.org/browse/JENKINS-34564?focusedCommentId=272709=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-272709] and it worked. Branches names are now strippedInstead.Before plugin update (was working):{code}/var/lib/jenkins/workspace/project/project/branch_name@script{code}After update (failing):{code}/var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E{code}Adding the following line to {{/etc/default/jenkins}}:{code}JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30"{code}Results in this:{code} /var/lib/jenkins/workspace/ r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script{code}Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash.In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too:{quote}{{/j}} folder, as opposed to {{/var/lib/jenkins}}.{quote}But not quite sure what's the best way to achieve this.Related SO Questions:http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-buildhttp://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Gabriel Le Breton commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. I updated my plugins recently and my builds stopped working. I tried Jesse Glick's suggestion and it worked. Branches names are now stripped Instead. Before plugin update (was working): /var/lib/jenkins/workspace/project/project/branch_name@script After update (failing): /var/lib/jenkins/workspace/project_project_master-0GR3K62UHM3ITQD3DYGVNX7HHRXYWN3NP946WC282P28PH4B061E Adding the following line to /etc/default/jenkins: JAVA_ARGS="-Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=30" Results in this: r-MQDDZ79AS4LC4V4O49CTXGW52GDS8XDTMLMAIS05Q0ZHJ2NKK19N@script Only one letter is kept from my branch but I don't really care as long as it works. Thanks for this. At this point, I would only keep generated hash. In case it doesn't solve for other people, Using a shorter path for workspace sounds a good idea too: /j folder, as opposed to /var/lib/jenkins. But not quite sure what's the best way to achieve this. Related SO Questions: http://stackoverflow.com/questions/17310959/is-there-any-way-to-change-the-working-directory-of-a-jenkins-maven-build http://stackoverflow.com/questions/21839538/change-jenkins-home-on-red-hat-linux Add Comment
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Yury Zaytsev commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. > which sounds like a bug in Python: it should use /usr/bin/env. Just for the record: this isn't a bug by any means. They do it on purpose, because installed modules should be bound to a specific installing interpreter for many reasons. The question is, can they apply some hacks on their side to work around limited shebang path length issue or not, but it's a tangential one, and, in any case, the latest status was that if one could think of something, they'd welcome patches. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. If we generate directory names that are ~80 characters long we can expect trouble. Depends entirely on what you are doing inside those directories. 80 characters is not really that long, and prior to the change directories prefixes could be much longer—unbounded, in fact (as noted in some complaints prior to the fix). (Note that you can customize the prefix length via system property.) PATH_MAX=40 No, anything less than 54 will not work at all, I just neglected to have that issue a warning. already tuned to workaround the shebang PATH limitations This really sounds like a separate issue, possibly in durable-task plugin, which should be filed separately with steps to reproduce from scratch—unless it is a limitation in the tools you are using: all I have seen so far is when you install any Python modules in a local prefix tree, it hardcodes the absolute path to the interpreter into the scripts which sounds like a bug in Python: it should use /usr/bin/env. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Sorin Sbarnea reopened an issue I am reopening this issue because clearly the new current behaviour is even worse than it was when the bug was opened in the first place. If we generate directory names that are ~80 characters long we can expect trouble. Not to mention that putting all of them in a single folder could generate some other scalability issues. Until we have a proper change of the default behaviour (what we really should have!) people encountering this can do add this to /etc/default/jenkins: -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=40 – probably it would be safe to put even a shorter value, like 20. The default number seems to be ridiculous high, somewhere between 80-90. This feature did broke out Jenkins which was already tuned to workaround the shebang PATH limitations by moving the home directory of Jenkins user to /j folder, as opposed to /var/lib/jenkins. This was enough for us but now is not anymore. Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Sorin Sbarnea Resolution: Fixed Status: Resolved Reopened Add Comment
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. (although in the case of Windows there are workarounds IIRC involving a magic path prefix that switches paths to UNC syntax internally) 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Jesse Glick resolved as Fixed bq, You have no simple way to get workspaces from org/project/branch/build which you can use in e.g. scripts. You should not be doing so. The workspaces are neither reused Yes they are. nor cleaned up If the job is deleted while the agent is online, the workspace is removed. Jenkins has more general issues here. You cannot use them on the console, not even with shell expansion, due to some starting with a "-" (ex. rm -r * in JENKINS_HOME/workspace fails) In general you should use --. Patches to ensure that the trimmed name does not start with - will be entertained of course (follow-up issues). The filename is very long. While not being an issue for us, many users have reported hitting MAXPATH with their projects on Windows. Yes; in general there is no foolproof solution for operating systems which impose path length limitations. Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Jesse Glick Status: Reopened Resolved Resolution: Fixed Add Comment
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Yury Zaytsev reopened an issue So, in addition to causing massive problems on Windows, this also causes trouble on Unix, if the workspace contains shell scripts which use binaries residing in the workspace as interpreters. That is, something like what follows: $ cat foo #!/home/jenkins/agent/workspace/xxx-O7T6IFSVMNBO5RYGRVNFUGEOPAZAIQ4GQRK47UUDIOZMEN3K2OAA/source/lib/python-san/install/bin/python-dbg One might think this ought to happen very rarely, but that's not the case! Basically, when you install any Python modules in a local prefix tree, it hardcodes the absolute path to the interpreter into the scripts and are you are screwed See here for the details on `#!` maximum length limits (127 bytes on Linux): http://www.in-ulm.de/~mascheck/various/shebang/ Jenkins / JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named. Change By: Yury Zaytsev Resolution: Fixed Status: Resolved Reopened Add Comment
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Hans Schulz edited a comment on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. # The new solution has multiple issues which makes it unusable for us:# You have no simple way to get workspaces from org/project/branch/build which you can use in e.g. scripts.# The workspaces are neither reused nor cleaned up, causing a "filesystem leak". No simple way to write a cleanup script because of #1# You cannot use them on the console, not even with shell expansion, due to some starting with a "-" (ex. rm -r * in JENKINS_HOME/workspace fails)# They do not reside in the job's directory anymore, so deleting a job does not delete the workspaces (and again, no simple mapping possible)# The filename is verry long. While not being an issue for us, many users have reported hitting MAXPATH with their projects on Windows.Why was just changing the escaping strategy to more sane characters not an option? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Hans Schulz edited a comment on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. The new solution has multiple issues which makes it unusable for us:# You have no simple way to get workspaces from org/project/branch/build which you can use in e.g. scripts.# The workspaces are neither reused nor cleaned up, causing a "filesystem leak". No simple way to write a cleanup script because of #1# You cannot use them on the console, not even with shell expansion, due to some starting with a "-" (ex. rm -r * in JENKINS_HOME/workspace fails)# They do not reside in the job's directory anymore, so deleting a job does not delete the workspaces (and again, no simple mapping possible)# The filename is verry very long. While not being an issue for us, many users have reported hitting MAXPATH with their projects on Windows.Why was just changing the escaping strategy to more sane characters not an option? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Iwo Olszewski commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. The new workspace naming schema can be disabled by setting the system property jenkins.branch.WorkspaceLocatorImpl.PATH_MAX to 0. Other values should control max length of generated directory name in new schema (but I didn't verified it). To be effective, this system property need to be set during Jenkins startup (e.g. by adding -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=0 as a param). 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.
