Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
Jenkins 2.263.3
P4-Plugin 1.11.2
Description
If a changelist is specified in scm: checkout, p4 polling does not work. The result is the specified changelist is used in the range:
P4: Polling with range: 53910841,53910841
p4 changes -m20 //clientname_/...@53910841,53910841
This result, is polling will not detect any subsequent changes.
If changelist is not specified during scm: checkout,
P4: Polling with range: 53910841,now
p4 changes -m20 //clientname_/...@53910841,now
P4 plugin should always use "now" for the higher end of the range, regardless if a changelist was specified or not.
Attachments
Activity
I think the issue is in PollTask.java, this usage of the 'pin' which is how you currently sync to a change in the p4 plugin is by using the pin. I think it shouldn't be using the pin at all and should just as the original reporter suggested, always poll latest.
Because pin is how you sync to a specific change, once you've done it polling will forever try to check for changes with that being the reference and the thing to compare against.
@Override public Object task(ClientHelper p4) throws Exception { List<P4Ref> changes = new ArrayList<P4Ref>(); // find changes... if (pin != null && !pin.isEmpty()) { changes = p4.listHaveChanges(lastRefs, new P4LabelRef(pin)); } else { changes = p4.listHaveChanges(lastRefs); }
It's getting that from PerforceScm.java:
private List<P4Ref> lookForChanges(FilePath buildWorkspace, Workspace ws, Run<?, ?> lastRun, TaskListener listener) throws IOException, InterruptedException { // Set EXPANDED client String syncID = ws.getSyncID(); // Set EXPANDED pinned label/change String pin = populate.getPin(); if (pin != null && !pin.isEmpty()) { pin = ws.getExpand().format(pin, false); ws.getExpand().set(ReviewProp.P4_LABEL.toString(), pin); } // Calculate last change, build if null (JENKINS-40356) List<P4Ref> lastRefs = TagAction.getLastChange(lastRun, listener, syncID); if (lastRefs == null || lastRefs.isEmpty()) { // no previous build, return null. listener.getLogger().println("P4: Polling: No changes in previous build."); return null; } // Create task PollTask task = new PollTask(credential, lastRun, listener, filter, lastRefs); task.setWorkspace(ws); task.setLimit(pin); // Execute remote task List<P4Ref> changes = buildWorkspace.act(task); return changes; }
Karl Wirth
added a comment - Hi kyates,
Thanks. I was having problems reproducing it, but just managed it. Assigning to the devs. They will review the defect during their next sprint review. I do not know when this will be but I will also highlight this to the product manager.
Reproduction steps for Dev:
(1) Create the following directory structure in Perforce:
//depot/PinPolled2/Jenkinsfile/Jenkinsfile //depot/PinPolled2/src/f1 //depot/PinPolled2/src/f2
and use the Jenkinsfile:
pipeline {
agent { label 'master' }
stages {
stage("Repro") {
steps {
script {
checkout perforce(credential: 'JenkinsMaster', populate: forceClean(have: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: params.PINCL, quiet: false), workspace: manualSpec(charset: 'none', cleanup: false, name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-SRC', pinHost: false, spec: clientSpec(allwrite: false, backup: true, changeView: '', clobber: true, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE', view: '//depot/PinPolled2/src/... //${P4_CLIENT}/...')))
}
}
}
}
}
(2) Create a new pipeline job with the string paramater "PINCL" with no default value and Jenkinsfile from SCM source:
//depot/PinPolled2/Jenkinsfile/... //${P4_CLIENT}/...
(3) Manually build the job with no paramater to set up polling.
(4) Submit a new file to 'src' subtree.
(5) Run 'Poll Now' (assumes poll now plugin installed).
(6) Correct changelist found.
(7) Submit two new files to 'src' subtree in seperate changelists.
(8) Manually build the job with paramater set to first changelist from step (7). Therefore we have not built head.
(9) Run 'Poll now' again. The changelist from step (8) is used as the lower and upper limit. For example it was CL 123 (pure coincidence 
) in my testing and head revision for 'src' was CL 124:
Perforce Software Polling Log Started on Jun 9, 2021 11:36:03 AM Executor number at runtime: 0 P4: Polling on: master with:jenkins-master-PinPolled2JenkinsfileNew-0 Found last change 121 on syncID jenkins-NODE_NAME-PinPolled2JenkinsfileNew-EXECUTOR_NUMBER ... p4 login -s + ... p4 client -o jenkins-master-PinPolled2JenkinsfileNew-0 + ... p4 info + ... p4 info +... p4 client -o jenkins-master-PinPolled2JenkinsfileNew-0 + P4 Task: establishing connection. ... server: 192.168.1.160:1666 ... node: vm-kwirth-swarm202-xenial P4: Polling with range: 121,now ... p4 changes -m20 //jenkins-master-PinPolled2JenkinsfileNew-0/...@121,now + ... p4 repos -C + P4: Polling no changes found. Executor number at runtime: 0 P4: Polling on: master with:jenkins-master-PinPolled2JenkinsfileNew-0-SRC Found last change 123 on syncID jenkins-NODE_NAME-PinPolled2JenkinsfileNew-EXECUTOR_NUMBER-SRC ... p4 login -s + ... p4 client -o jenkins-master-PinPolled2JenkinsfileNew-0-SRC + ... p4 info + ... p4 info + ... p4 client -o jenkins-master-PinPolled2JenkinsfileNew-0-SRC + P4 Task: establishing connection. ... server: 192.168.1.160:1666 ... node: vm-kwirth-swarm202-xenial P4: Polling with range: 123,123 ... p4 changes -m20 //jenkins-master-PinPolled2JenkinsfileNew-0-SRC/...@123,123 + ... p4 repos -C +P4: Polling no changes found. Done. Took 55 ms No changes
Note the "p4 changes -m20 //jenkins-master-PinPolled2JenkinsfileNew-0-SRC/...@123,123".
Karl Wirth
added a comment - Hi kyates ,
Thanks. I was having problems reproducing it, but just managed it. Assigning to the devs. They will review the defect during their next sprint review. I do not know when this will be but I will also highlight this to the product manager.
Reproduction steps for Dev:
(1) Create the following directory structure in Perforce:
//depot/PinPolled2/Jenkinsfile/Jenkinsfile
//depot/PinPolled2/src/f1
//depot/PinPolled2/src/f2
and use the Jenkinsfile:
pipeline {
agent { label 'master' }
stages {
stage( "Repro" ) {
steps {
script {
checkout perforce(credential: 'JenkinsMaster' , populate: forceClean(have: false , parallel: [enable: false , minbytes: '1024' , minfiles: '1' , threads: '4' ], pin: params.PINCL, quiet: false ), workspace: manualSpec(charset: 'none' , cleanup: false , name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-SRC' , pinHost: false , spec: clientSpec(allwrite: false , backup: true , changeView: '', clobber: true , compress: false , line: ' LOCAL ', locked: false , modtime: false , rmdir: false , serverID: ' ', streamName: ' ', type: ' WRITABLE ', view: ' //depot/PinPolled2/src/... //${P4_CLIENT}/...')))
}
}
}
}
}
(2) Create a new pipeline job with the string paramater "PINCL" with no default value and Jenkinsfile from SCM source:
//depot/PinPolled2/Jenkinsfile/... //${P4_CLIENT}/...
(3) Manually build the job with no paramater to set up polling.
(4) Submit a new file to 'src' subtree.
(5) Run 'Poll Now' (assumes poll now plugin installed).
(6) Correct changelist found.
(7) Submit two new files to 'src' subtree in seperate changelists.
(8) Manually build the job with paramater set to first changelist from step (7). Therefore we have not built head.
(9) Run 'Poll now' again. The changelist from step (8) is used as the lower and upper limit. For example it was CL 123 (pure coincidence ) in my testing and head revision for 'src' was CL 124:
Perforce Software Polling Log
Started on Jun 9, 2021 11:36:03 AM
Executor number at runtime: 0
P4: Polling on: master with:jenkins-master-PinPolled2JenkinsfileNew-0
Found last change 121 on syncID jenkins-NODE_NAME-PinPolled2JenkinsfileNew-EXECUTOR_NUMBER
... p4 login -s +
... p4 client -o jenkins-master-PinPolled2JenkinsfileNew-0 +
... p4 info +
... p4 info +... p4 client -o jenkins-master-PinPolled2JenkinsfileNew-0 +
P4 Task: establishing connection.
... server: 192.168.1.160:1666
... node: vm-kwirth-swarm202-xenial
P4: Polling with range: 121,now
... p4 changes -m20 //jenkins-master-PinPolled2JenkinsfileNew-0/...@121,now +
... p4 repos -C +
P4: Polling no changes found.
Executor number at runtime: 0
P4: Polling on: master with:jenkins-master-PinPolled2JenkinsfileNew-0-SRC
Found last change 123 on syncID jenkins-NODE_NAME-PinPolled2JenkinsfileNew-EXECUTOR_NUMBER-SRC
... p4 login -s +
... p4 client -o jenkins-master-PinPolled2JenkinsfileNew-0-SRC +
... p4 info +
... p4 info +
... p4 client -o jenkins-master-PinPolled2JenkinsfileNew-0-SRC +
P4 Task: establishing connection.
... server: 192.168.1.160:1666
... node: vm-kwirth-swarm202-xenial
P4: Polling with range: 123,123
... p4 changes -m20 //jenkins-master-PinPolled2JenkinsfileNew-0-SRC/...@123,123 +
... p4 repos -C +P4: Polling no changes found.
Done. Took 55 ms
No changes
Note the "p4 changes -m20 //jenkins-master-PinPolled2JenkinsfileNew-0-SRC/...@123,123".
p4karl, I provided 288148 and that's what the build.xml shows.
<org.jenkinsci.plugins.p4.tagging.TagAction plugin="p4@1.11.5"> <tags/> <refChanges> <org.jenkinsci.plugins.p4.changes.P4ChangeRef> <change>288148</change> </org.jenkinsci.plugins.p4.changes.P4ChangeRef> </refChanges>Leaving it as an empty string results in the same changes to build.xml. I use the empty string for the latest, I've never used 'now'.
Here's the polling log even though 288159 has changes, the polling isn't polling anything past the provided changelist.
P4: Polling with range: 288148,288148 ...tick... ... p4 changes -m10 //*****/...@288148,288148 + ... p4 repos -C + P4: Polling no changes found. P4: Polling no changes found. no polling baseline in *****