| Mykola Ulianytskyi - Behavior confirmed. Forwarding to development team. Even though 'poll: false' is set we are still creating a SyncID and polling for the second sync. My test was simpler all on the master:
pipeline {
agent { label 'master' }
stages {
stage("Repro") {
steps {
script {
echo "Starting"
checkout poll: true, scm: perforce(credential: 'JenkinsMasterAdminUser', populate: autoClean(delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: false, replace: true, tidy: false), workspace: manualSpec(charset: 'none', cleanup: false, name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-sub1', 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/pipeline_poll_false/sub1/... //${P4_CLIENT}/...')))
checkout poll: false, scm: perforce(credential: 'JenkinsMasterAdminUser', populate: autoClean(delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: false, replace: true, tidy: false), workspace: manualSpec(charset: 'none', cleanup: false, name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-sub2', 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/pipeline_poll_false/sub2/... //${P4_CLIENT}/...')))
sh 'echo WS IS $P4_CLIENT'
}
}
}
}
}
SyncIDs I see are:
Perforce Software Polling Log
Started on Feb 25, 2019 4:51:07 PM
P4: Polling on: master with:jenkins-master-Pipeline_Poll_False_Test2-0
Found last change 246 on syncID jenkins-NODE_NAME-Pipeline_Poll_False_Test2-EXECUTOR_NUMBER
... p4 client -o jenkins-master-Pipeline_Poll_False_Test2-0 +
... p4 info +
... p4 info +
... p4 client -o jenkins-master-Pipeline_Poll_False_Test2-0 +
... No change in client detected.
P4 Task: establishing connection.
... server: vm-kwirth-swarm182-xenial:1666
... node: vm-kwirth-swarm182-xenial
P4: Polling with range: 246,now
... p4 changes -m20 //jenkins-master-Pipeline_Poll_False_Test2-0/...@246,now +
... p4 repos -C +
P4: Polling on: master with:jenkins-master-Pipeline_Poll_False_Test2-0-sub1
Found last change 242 on syncID jenkins-NODE_NAME-Pipeline_Poll_False_Test2-EXECUTOR_NUMBER-sub1
... p4 client -o jenkins-master-Pipeline_Poll_False_Test2-0-sub1 +
... p4 info +
... p4 info +
... p4 client -o jenkins-master-Pipeline_Poll_False_Test2-0-sub1 +
... No change in client detected.
P4 Task: establishing connection.
... server: vm-kwirth-swarm182-xenial:1666
... node: vm-kwirth-swarm182-xenial
P4: Polling with range: 242,now
... p4 changes -m20 //jenkins-master-Pipeline_Poll_False_Test2-0-sub1/...@242,now +
... p4 repos -C +
P4: Polling on: master with:jenkins-master-Pipeline_Poll_False_Test2-0-sub2
Found last change 247 on syncID jenkins-NODE_NAME-Pipeline_Poll_False_Test2-EXECUTOR_NUMBER-sub2
... p4 client -o jenkins-master-Pipeline_Poll_False_Test2-0-sub2 +
... p4 info +
... p4 info +
... p4 client -o jenkins-master-Pipeline_Poll_False_Test2-0-sub2 +
... No change in client detected.
It should not be polling on on syncID "jenkins-NODE_NAME-Pipeline_Poll_False_Test2-EXECUTOR_NUMBER-sub2". |
