-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Windows
-
-
2.1.2
After a recent update, slashes in git branches (e.g. bugfix/branch-description) are escaped into workspace path names using %2F, as in wkspacepath/bugfix%2Fbranch-description. This breaks the build on my windows machine. The slashes used to be translated to underscores.
- is related to
-
JENKINS-60785 corrupt workspaces.txt file on agent, changes multibranch builds to use workspace directory with slash converted to %2F, causing errors
-
- Open
-
- relates to
-
JENKINS-21942 Unreliable defaulting of Jenkins.workspaceDir
-
- Open
-
-
JENKINS-44360 '%' in branch name causes GitHub multi-branch job failures
-
- Open
-
-
JENKINS-54640 Workspace folders are not unique
-
- Closed
-
-
JENKINS-2111 removing a job (including multibranch/org folder branches/repos) does not remove the workspace
-
- Resolved
-
- links to
This problem appeared after I did an upgrade. I tried to restore to previous version and plugins but problem persisted. I enabled a log as noted above and found a message:
JENKINS-2111path sanitization ineffective when using legacy workspace root directory c:\JenkinsWorkspace\${ITEM_FULLNAME}; switch to ${JENKINS_HOME}/workspace/${ITEM_FULLNAME}so I did and its working now!
This did move to a new workplace so all the directories are now so I don't know if that fixed it or the form of the path. Note the slashes were reversed. Before this Jenkins was creating a working directory simply with the first part of the name , e.g. QA/V2018 became QA