I updated a Jenkins build system today and pipeline builds no longer worked. After an hour or two of debugging I figured out it was due to the Jenkinsfile not being checked out due to the Jenkins / the P4 plugin having changed the location (path) it checked out to. Checking out p4-12b39e21-cb2b-47e8-9488-22aca324fc36-//ir/rana/ebf/10.0.0/products/jenkins/linux/Jenkinsfile //jenkins-${NODE_NAME}-${JOB_NAME}/Jenkinsfile into /var/lib/jenkins/jobs/IIRV10-linux-ebf/branches/IIRV10ebf/workspace@script to read Jenkinsfile ... ERROR: /var/lib/jenkins/jobs/IIRV10-linux-ebf/branches/IIRV10ebf/workspace@script/Jenkinsfile not found Finished: FAILURE The previous path used was /var/lib/jenkins/workspace/V10-build-trunk_IIRV10trunk-M5WSRVTJ6TYJGMXQO4574D5VYI3DULEPQJZJY5FGST6MOUHDDAPQ%40script The change simplifies the generated path so is a good change. The problem is that Perforce thinks it is already checked out and so does not get the file. From the command line you woul
Random thoughts and idle musings