-
Bug
-
Resolution: Fixed
-
Critical
-
Jenkins 2.151
pipeline 2.5
pipeline-multibranch 2.20
-
-
2.1.1
Something changed in the naming of the workspace folders on the Jenkins Master node. Previously, the name the was suffixed with a long random (names are examples only, the exact length is different):
MyProjectA1_MyBranch-ZOBMWQA2JSVUZRAPJAQ3NT3TSBIUQOS26N5CF3XJB@libs MyProjectA1_MyBranch-ZOBMWQA2JSVUZRAPJAQ3NT3TSBIUQOS26N5CF3XJB@script MyVeryLongBranchName-NHOUUZPM5MARPAN7OGASNLPNCKRLL26RQKEZIEEKC@libs MyVeryLongBranchName-NHOUUZPM5MARPAN7OGASNLPNCKRLL26RQKEZIEEKC@script MyVeryLongBranchName-TN6NSHXVGMKRKUOVV7CKNODZOK3JSHI4CQYCOR4E6@libs MyVeryLongBranchName-TN6NSHXVGMKRKUOVV7CKNODZOK3JSHI4CQYCOR4E6@script
However now, this suffix seems to be removed, causing name clashes when different repositories have long but identical branch names:
MyProjectA1_MyBranch@libs MyProjectA1_MyBranch@script MyVeryLongBranchName@libs <<-\ MyVeryLongBranchName@script | <<-\ MyVeryLongBranchName@libs <<-/ | MyVeryLongBranchName@script <<-/
The last two repositories are unrelated but map to the same directory, causing "unrelated repository" errors during checkout.
- relates to
-
JENKINS-2111 removing a job (including multibranch/org folder branches/repos) does not remove the workspace
- Resolved
-
JENKINS-38706 Workspace directory names mangled in multibranch pipeline
- Resolved
-
JENKINS-54654 A recent update breaks builds by escaping slashes to percent signs in workspace paths
- Resolved
- links to