[JIRA] (JENKINS-49525) Rare exception sync'ing global pipeline library with new project

[kwi...@perforce.com (JIRA)]

Title: Message Title

Karl Wirth commented on JENKINS-49525   Re: Rare exception sync'ing global pipeline library with new project Cannot reproduce the problem but I do see we use the same workspace name to sync the libarries but different locations: $ p4 print -a //spec/client/jenkins-library.p4s | grep Root | grep -v "#" Root:    /var/lib/jenkins/workspace/FirstJob%40libs/my-shared-library Root:    /var/lib/jenkins/workspace/AnotherJob%40libs/my-shared-library Note in the above the same client 'jenkins-library' is used by both jobs to sync the shared library but the workspace 'Root:' is being changed to be a variation on the job name. This could in theorey cause a problem so should be changed.   FYI - My global library configuration: Possible resolutions: Plugin uses one global location workspace rooted in the same place based on Library Name (although Paul may have said Jenkins does not expose this information). Plugin uses one global library directory per library per job (don't know what the jenkins sync rules are for global libraries). Add Comment   This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.