This is very strange and I hadn't been able to nail it yet since it happened inconsistently where sometimes the p4 plugin would essentially use the ${JENKINS_HOME} as the root and sometimes use the ${WORKSPACE} as the root (as far as I can tell)...  The ${WORKSPACE} is what we wanted it to use.

So, even within the same "job"; this will happen. 

Our Workspace Name within the Perforce Software is specified to be jenkins-pdkmfg-${JOBNAME}.  

If I looked at the console logs, or that I check the p4 client:

p4 client -o jenkins-pdkmfg-my_job_name

I would see the root defined as

/proj/gde_pdk_scratch/jenkins/prod/p4/worksapce/my_job_name

which is where our workspace is defined and which is what we wanted, but sometimes also as:

/home/pdkmfg/tools/prod/jenkins_home

which caused a lot of problems...  Sometimes it would just fail; but on some occasion, our jenkins_home got wiped (I think that is because some of our jobs we set the Auto Clean or Force Sync.)

What could cause P4 plugin to use JENKINS_HOME as root instead of WORKSPACE or if there is a way for me to make sure that it is using WORKSPACE.

Thanks and Regards...