[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Paul Allen commented on JENKINS-56248 Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false) TODO: retest this issue after updating plugin dependencies. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197815.1550844551000.1633.1575559080449%40Atlassian.JIRA.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-56248 P4Plugin Polls Workspaces With Disabled Polling (poll: false) Change By: Paul Allen Priority: Blocker Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197815.1550844551000.1623.1575559020719%40Atlassian.JIRA.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Karl Wirth commented on JENKINS-56248 Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false) Hi Adam Smith - I'm just support sorry. Charusheela Bopardikar - Can you take another look at this. Thanks in advance. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197815.1550844551000.7763.1574865720633%40Atlassian.JIRA.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Karl Wirth edited a comment on JENKINS-56248 Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false) Hi [~asmith_pipeworks] - I'm just support sorry. [~cbopardikar] - Can you take another look at this . ? Thanks in advance. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197815.1550844551000.7773.1574865720740%40Atlassian.JIRA.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Adam Smith commented on JENKINS-56248 Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false) Thank you for the workaround Charusheela Bopardikar, this fixed my use case (which is using manualSpec). That said, this has been in backlog for 9 months now – any progress here Karl Wirth? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197815.1550844551000.7360.1574798520295%40Atlassian.JIRA.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Mykola Ulianytskyi commented on JENKINS-56248 Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false) Meanwhile, I tested below workaround as suggested by Paul Allen and it has exactly the same effect as the PR without any code change. The workaround doesn't work for streamSpec. It can be used only with manualSpec. PR fixes the issue with streamSpec. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197815.1550844551000.7077.1561365000840%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title
Charusheela Bopardikar edited a comment on JENKINS-56248
Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false)
The code change as suggested in the PR will have an impact on other customers. Need to do a thorough analysis before accepting the PR.Meanwhile, I tested below workaround as suggested by [~p4paul] and it has exactly the same effect as the PR without any code change.Changed the view mapping to make it unique using the name parameter since ${P4_CLIENT} is not expanded when the key is evaluated. view: '//depot/pipeline_poll_false/sub1/... //jenkins-${NODE_NAME} - ${JOB_NAME} - ${EXECUTOR_NUMBER}-sub1/...'andview: '//depot/pipeline_poll_false/sub1/... //jenkins-${NODE_NAME} - ${JOB_NAME} - ${EXECUTOR_NUMBER}-sub2/...' So, the script looks like this:{code:xml}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/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-sub1/...'))) 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/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-sub2/...'))) sh 'echo WS IS $P4_CLIENT'} }} }}{code}
Add Comment
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title
Charusheela Bopardikar edited a comment on JENKINS-56248
Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false)
The code change as suggested in the PR will have an impact on other customers. Need to do a thorough analysis before accepting the PR.Meanwhile, I tested this below workaround as suggested by [~p4paul] and it has exactly the same effect as the PR without any code change. Changed the pipeline script as below view mapping to make it unique using the name parameter since ${P4_CLIENT} is not expanded when the key is evaluated . view: '//depot/pipeline_poll_false/sub1/... //jenkins-$ { NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-sub1/...'andview: '//depot/pipeline_poll_false/sub1/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-sub2/...' So, the script looks like this:{ code:xml}pipeline { agent { label 'master' } stages {stage("Repro") { steps {script { echo "Starting" checkout poll: true, changelog:true, scm: perforce(credential: ' perforceAdmin 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}- pack1 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/ projC pipeline_poll_false / main sub1 / src/pack1/ ... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}- pack1 sub1 /...'))) sh 'echo WS IS $P4_CLIENT' checkout poll: false, changelog:false, scm: perforce(credential: ' perforceAdmin 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}- pack2 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/ projC pipeline_poll_false / main sub2 / src/pack2/ ... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}- pack2 sub2 /...'))) sh 'echo WS IS $P4_CLIENT'} }} }}{code}
Add Comment
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title
Charusheela Bopardikar edited a comment on JENKINS-56248
Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false)
The code change as suggested in the PR will have an impact on other customers. Need to do a thorough analysis before accepting the PR.Meanwhile, I tested this workaround as suggested by [~p4paul] and it has exactly the same effect as the PR without any code change. Changed the pipeline script as below. { {{ code:xml} }} pipeline { agent \ { label 'master' } stages { stage("Repro") { steps { script { echo "Starting" checkout poll: true, changelog:true, scm: perforce(credential: 'perforceAdmin', 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}-pack1', 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/projC/main/src/pack1/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-pack1/...'))) sh 'echo WS IS $P4_CLIENT' checkout poll: false, changelog:false, scm: perforce(credential: 'perforceAdmin', 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}-pack2', 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/projC/main/src/pack2/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-pack2/...'))) sh 'echo WS IS $P4_CLIENT' } } } }} { {{ code} }}{{}}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title
Charusheela Bopardikar commented on JENKINS-56248
Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false)
The code change as suggested in the PR will have an impact on other customers. Need to do a thorough analysis before accepting the PR. Meanwhile, I tested this workaround as suggested by Paul Allen and it has exactly the same effect as the PR without any code change. Changed the pipeline script as below. {{
}}
pipeline {
agent \{ label 'master' }
stages {
stage("Repro") {
steps {
script {
echo "Starting"
checkout poll: true, changelog:true, scm: perforce(credential: 'perforceAdmin', 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}-pack1', 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/projC/main/src/pack1/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-pack1/...')))
sh 'echo WS IS $P4_CLIENT'
checkout poll: false, changelog:false, scm: perforce(credential: 'perforceAdmin', 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}-pack2', 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/projC/main/src/pack2/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-pack2/...')))
sh 'echo WS IS $P4_CLIENT'
}
}
}
}
}
{{
}} {{}}
Add Comment
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Charusheela Bopardikar commented on JENKINS-56248 Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false) Tested pull request https://github.com/jenkinsci/p4-plugin/pull/95 and looks to be working fine with Jenkins version 2.164.3. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197815.1550844551000.25133.1560259440979%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Mykola Ulianytskyi commented on JENKINS-56248 Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false) Jenkins 2.164.3 has the same behavior as 2.150.3. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197815.1550844551000.21039.1559657820306%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Paul Allen commented on JENKINS-56248 Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false) Need to verify. Please test with the latest version of jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197815.1550844551000.21029.1559657460246%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Paul Allen assigned an issue to Charusheela Bopardikar Jenkins / JENKINS-56248 P4Plugin Polls Workspaces With Disabled Polling (poll: false) Change By: Paul Allen Assignee: Charusheela Bopardikar Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197815.1550844551000.21020.1559657340319%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-56248 P4Plugin Polls Workspaces With Disabled Polling (poll: false) Change By: Karl Wirth Labels: P4_A P4_B Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title
Mykola Ulianytskyi updated an issue
Jenkins / JENKINS-56248
P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Change By:
Mykola Ulianytskyi
HelloP4Plugin polls all workspaces used in job even if poll parameter is disabled in checkout.h2. Steps to reproduce # Create pipeline job test4 (see below) # Start pipeline job test4 # See "Perforce Software Polling Log" and Perforce Server Log {code:java}pipeline { agent(none) options { ansiColor("xterm") buildDiscarder(logRotator(numToKeepStr: "10")) disableConcurrentBuilds() disableResume() skipDefaultCheckout(true) timestamps() } triggers { pollSCM("* * * * *") } stages { stage("Master") { agent { label("master") } steps { checkout perforce(credential: 'perforce-ticket-jenkins', populate: flushOnly(pin: '', quiet: false), workspace: streamSpec(charset: 'none', format: 'test4-master', pinHost: true, streamName: '//playground/jenkins-main')) } } stage("Win-1") { agent { label("k02-bld-win-01") } steps { checkout changelog: false, poll: false, scm: perforce(credential: 'perforce-ticket-jenkins', populate: flushOnly(pin: '', quiet: false), workspace: streamSpec(charset: 'none', format: 'test4-win-1', pinHost: true, streamName: '//playground/jenkins-main')) } } stage("Win-2") { agent { label("k02-bld-win-02") } steps { checkout changelog: false, poll: false, scm: perforce(credential: 'perforce-ticket-jenkins', populate: flushOnly(pin: '', quiet: false), workspace: streamSpec(charset: 'none', format: 'test4-win-2', pinHost: true, streamName: '//playground/jenkins-main')) } } }}{code} h2. Perforce Software Polling Log {code:java}Started on Feb 22, 2019 3:45:00 PMP4: Polling on: master with:test4-masterFound last change 1180191 on syncID test4-master... p4 client -o test4-master +... p4 info +... p4 info +... p4 client -o test4-master +... No change in client detected. P4 Task: establishing connection server: perforce:1666... node: k02-jenkinsP4: Polling with range: 1180191,now... p4 changes -m20 //test4-master/...@1180191,now +... p4 repos -C +P4: Polling on: master with:test4-win-1Found last change 1180191 on syncID test4-win-1... p4 client -o test4-win-1 +... p4 info +... p4 info +... p4 client -o test4-win-1 +... No change in client detected. P4 Task: establishing connection server: perforce:1666... node: k02-jenkinsP4: Polling with range: 1180191,now... p4 changes -m20 //test4-win-1/...@1180191,now +... p4 repos -C +P4: Polling on: master with:test4-win-2Found last change 1180191 on syncID test4-win-2... p4 client -o test4-win-2 +... p4 info +... p4 info +... p4 client -o test4-win-2 +... No chang
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-56248 P4Plugin Polls Workspaces With Disabled Polling (poll: false) Change By: Karl Wirth Labels: P4_SUPPORT P4_A Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Karl Wirth assigned an issue to Unassigned Jenkins / JENKINS-56248 P4Plugin Polls Workspaces With Disabled Polling (poll: false) Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title
Karl Wirth commented on JENKINS-56248
Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false)
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:j
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-56248 P4Plugin Polls Workspaces With Disabled Polling (poll: false) Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-56248 P4Plugin Polls Workspaces With Disabled Polling (poll: false) Change By: Karl Wirth Labels: P4_SUPPORT Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title Karl Wirth commented on JENKINS-56248 Re: P4Plugin Polls Workspaces With Disabled Polling (poll: false) Hi Mykola Ulianytskyi, Thanks for highlighting this. I will try to repro it and let you know my findings. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56248) P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Title: Message Title
Mykola Ulianytskyi created an issue
Jenkins / JENKINS-56248
P4Plugin Polls Workspaces With Disabled Polling (poll: false)
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2019-02-22 14:09
Environment:
Jenkins: 2.150.3 (official docker image) P4 Plugin: 1.9.6
Priority:
Blocker
Reporter:
Mykola Ulianytskyi
Hello P4Plugin polls all workspaces used in job even if poll parameter is disabled in checkout. Steps to reproduce
Create pipeline job test4 (see below)
Start pipeline job test4
See "Perforce Software Polling Log" and Perforce Server Log
pipeline {
agent(none)
options {
ansiColor("xterm")
buildDiscarder(logRotator(numToKeepStr: "10"))
disableConcurrentBuilds()
disableResume()
skipDefaultCheckout(true)
timestamps()
}
triggers {
pollSCM("* * * * *")
}
stages {
stage("Master") {
agent {
label("master")
}
steps {
checkout perforce(credential: 'perforce-ticket-jenkins', populate: flushOnly(pin: '', quiet: false),
workspace: streamSpec(charset: 'none', format: 'test4-master', pinHost: true, streamName: '//playground/jenkins-main'))
}
}
stag
