[JIRA] (JENKINS-59300) p4-plugin sets client root to null with template workspaces

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

Title: Message Title

Karl Wirth created an issue   Jenkins / JENKINS-59300 p4-plugin sets client root to null with template workspaces Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-09-10 15:00 Environment: P4 Plugin 1.10.3 Jenkins 1.276.1 Labels: P4_VERIFY Priority: Minor Reporter: Karl Wirth A poll will always set the workspace root to null when using template workspaces.   Reproduction steps: (1) Create a freestyle job using a template workspace using the workspace naming convention 'jenkins-${JOB_NAME}'. (2) Set it to not run concurrent executions and pin to a specific node. This is important because the workspace name is invalid if it need to run concurrently or on more than one node. (3) Set it's build trigger to be polling. (4) Build the job. A client is created with a valid root. (5) Run 'Poll Now'. The workspace root is set to 'null'. For example: Client: jenkins-nullRoot Update: 2019/09/10 14:00:40 Access: 2019/09/10 14:00:00 Owner: admin Root: null Options: noallwrite noclobber nocompress unlocked nomodtime normdir SubmitOptions: submitunchanged LineEnd: local View: //depot/00342303-nullRoot/... //jenkins-nullRoot/... Suggested Workaround: Include '${NODE_NAME}' in the workspace name and run on a slave that is not the master where polling occurs. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201847.1568127629000.712.1568127660149%40Atlassian.JIRA.