Details
-
Improvement
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
Description
The %2F encoding of / breaks many software (msbuild for example) and can't be changed.
Being able to provide a rule to build the subproject names from the branch name instead of just encoding things would permit to give the user the power to work around their problems with this kind of software.
This would be an advanced option in which one can write something like a sed regex.
Attachments
Issue Links
- duplicates
-
JENKINS-30744 multibranch issues if branch contains /
-
- Closed
-
- is blocked by
-
JENKINS-44360 '%' in branch name causes GitHub multi-branch job failures
-
- Open
-
-
JENKINS-44784 Branch indexing blocked by workspace cleanup hung on bad connection
-
- Resolved
-
- is duplicated by
-
JENKINS-37711 Percent encoding cause fail in Visual Studio
-
- Resolved
-
-
JENKINS-34475 github-org folder is incompatible with git flow implementations - branch names break builds
-
- Resolved
-
-
JENKINS-38706 Workspace directory names mangled in multibranch pipeline
-
- Resolved
-
-
JENKINS-34595 Multibranch Pipeline Project vs SVN branches
-
- Resolved
-
-
JENKINS-37677 Handle jobs in Multibranch projects where git branches have special characters
-
- Resolved
-
-
JENKINS-37045 Don't use "%2F" in branch directory name
-
- Resolved
-
-
JENKINS-35633 multibranch builds with visual studio incorrectly handles branches with a slash
-
- Closed
-
-
JENKINS-32239 job naming sould be configurable
-
- Resolved
-
-
JENKINS-32253 Want an option to encode slashes in branch names differently
-
- Resolved
-
-
JENKINS-42923 Multibranch job should have an option to shorten the job/script directory
-
- Resolved
-
-
JENKINS-38874 Shorten branch's folder name
-
- Closed
-
- is related to
-
JENKINS-34083 Compilation problems
-
- Resolved
-
-
JENKINS-38837 Mutibranch project plugin does not respect "Workspace Root Directory" global configuration
-
- Resolved
-
- relates to
-
JENKINS-2111 removing a job (including multibranch/org folder branches/repos) does not remove the workspace
-
- Resolved
-
-
JENKINS-30148 Allocate shorter workspace if it will be too long for reasonable use inside build
-
- Open
-
-
JENKINS-51811 KubernetesSlave should override getWorkspaceFor(TopLevelItem)
-
- Open
-
- links to
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-2111is 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.