[JIRA] (JENKINS-54640) Workspace folders are not unique

[k...@vandewiele.com (JIRA)]

Title: Message Title

kpop created an issue   Jenkins / JENKINS-54640 Workspace folders are not unique Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-11-15 09:18 Environment: Jenkins 2.151 Priority: Critical Reporter: kpop 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. 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.