Upgraded to 1.8.7 and this has broken all jobs on our instance which use the JOB_NAME variable for workspace name/mapping.

Looking at the failed jobs, I can see that the ${JOB_NAME} variable used for both the Workspace name and list of mappings is being treated differently.

Consider the output below.

p4 client -o syd_jenkins_NightlyTesting-BUILD_COMPILER-clang-3.5.0

... p4 client -i +
P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.
Mapping '//syd_jenkins_NightlyTesting/BUILD_COMPILER=clang-3.5.0/...' is not under '//syd_jenkins_NightlyTesting-BUILD_COMPILER-clang-3.5.0/...'.

The job configuration contains a workspace name of {{syd_jenkins_\$
{JOB_NAME} }}and there are a list of mappings for this workspace that take the form of:

//Depot/core/dummy/... //syd_jenkins_${JOB_NAME}/...

From the output above, I believe the expansion of the JOB_NAME variable is treated differently within the two fields, rendering the 1.8.7 release of the P4 plugin unusable for anyone running in this manner.

I have downgraded to 1.8.6 in the interim and this has resolved the issue.