-
Bug
-
Resolution: Won't Fix
-
Critical
-
Windows 2012 x64, Java 1.8, Jenkins 2.7.4, Pipeline: Multibranch 2.9, Pipeline: API 2.4, Linux Python
Apparently after a recent update of plugins, our Multibranch Pipeline jobs started putting their workspaces in mangled locations. They used to be, for example, in D:\jenkins\cm-jenkins-09\my-pipline-job\my-branch-name and now they're like D:\jenkins\cm-jenkins-09\ine-job_my-banch-name-5P5URKHPJXWGGVIWDQOJBB3N7RJECAQJGFTDCVOPY3PABO7LNTIQ
There are several problems with this:
- They're difficult to read with all that garbage at the end, and the beginning of the name sometimes cut off
- They're not organized within the parent job like they used to be
- This is causing files within them to have extremely long paths such that Windows won't actually let us delete them (Jenkins, CMD, and Windows Explorer all fail to delete them)
Let me know if I can provide any other information to help solve this. This is a private Jenkins install so I can't point you to it.
- duplicates
-
JENKINS-38506 Invalid workspace path for pipeline jobs on jenkins master
- Resolved
-
JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named.
- Resolved
- is duplicated by
-
JENKINS-49251 Pipeline in Multi-branch mode creates too long workspace folder name
- Resolved
-
JENKINS-40072 Multibranch creates multiple new directories
- Closed
-
JENKINS-48176 Reduce length of workspace directory name for multibranch jobs
- Resolved
- relates to
-
JENKINS-2111 removing a job (including multibranch/org folder branches/repos) does not remove the workspace
- Resolved
-
JENKINS-54640 Workspace folders are not unique
- Closed
-
JENKINS-52911 Higly voted critical issue JENKINS-38706 remains unassigned in JIRA
- Resolved