[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth closed an issue as Not A Defect Jenkins / JENKINS-58456 explain polling per change Change By: Karl Wirth Status: Resolved Closed 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.200589.1562912637000.7806.1574867820215%40Atlassian.JIRA.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title
Hokwang Lee edited a comment on JENKINS-58456
Re: explain polling per change
[~p4karl],Thanks for your reply. So, if I use {code:java}filter: [incremental(true)],{code}in checkout syntax in Pipeline,I don't need to check Polling per Change in Polling build filters. Right?
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.200589.1562912637000.5280.1567491300275%40Atlassian.JIRA.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Hokwang Lee commented on JENKINS-58456 Re: explain polling per change So, if I use filter: [incremental(true)], in checkout syntax in Pipeline, I don't need to check Polling per Change in Polling build filters. Right? 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.200589.1562912637000.5278.1567491300249%40Atlassian.JIRA.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title
Karl Wirth updated an issue
Jenkins / JENKINS-58456
explain polling per change
Change By:
Karl Wirth
Comment:
Believe I have reproduced this. Reproduction steps:(1) Create a workspace in ws(2) Create files in "/ws/JENKINS-58639"(3) Created "/ws/JENKINS-58639/Jenkinsfile":{code:java}pipeline { options {skipDefaultCheckout() } agent { label 'docker-slave' } stages {stage("Sync") { steps { script{ checkout perforce(credential: 'JenkinsMaster', filter: [incremental(true)], populate: syncOnly(force: false, have: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, revert: false), workspace: templateSpec(charset: 'none', format: 'jenkins-${NODE_NAME}-${JOB_NAME}-src', pinHost: false, templateName: "JENKINS-58639-template")) } }}stage ("wait_prior_starting_smoke_testing") { steps { echo 'Waiting 20 seconds' sleep 30 }}stage("Test") { steps { sh 'ls' }} }}{code}(4) Create a job with!image-2019-09-02-16-25-39-289.png!!image-2019-09-02-16-25-59-683.png!!image-2019-09-02-16-26-19-383.png!!image-2019-09-02-16-26-46-699.png!(5) Set quiet period to 5 (not so important).(6) Build job once.(7) Submit a file to '/ws/JENKINS-58639'.(8) Add a trigger to perforce to slow down syncs. For example create script "sleep.sh":{code:java}echo Sleeping for 600s in trigger...sleep 600{code}make the file executable, then create a trigger entry:{code:java} trigger.sleep.1 command pre-user-sync ./sleep.sh{code}(9) Run Poll now. Job will wait 5 seconds then start building.(10) Submit another changelist to '/ws/JENKINS-58639'.(11) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building.(12) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building.(13) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building.(14) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building.
Add Comment
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title
Karl Wirth commented on JENKINS-58456
Re: explain polling per change
Believe I have reproduced this. Reproduction steps: (1) Create a workspace in ws (2) Create files in "/ws/JENKINS-58639" (3) Created "/ws/JENKINS-58639/Jenkinsfile":
pipeline {
options {
skipDefaultCheckout()
} agent { label 'docker-slave' } stages {
stage("Sync") {
steps {
script{
checkout perforce(credential: 'JenkinsMaster', filter: [incremental(true)], populate: syncOnly(force: false, have: true, modtime: false, parallel: [enable: false, minb
ytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, revert: false), workspace: templateSpec(charset: 'none', format: 'jenkins-${NODE_NAME}-${JOB_NAME}-src', pinHost:
false, templateName: "JENKINS-58639-template"))
}
}
}
stage ("wait_prior_starting_smoke_testing") {
steps {
echo 'Waiting 20 seconds'
sleep 30
}
}
stage("Test") {
steps {
sh 'ls'
}
}
}
}
(4) Create a job with (5) Set quiet period to 5 (not so important). (6) Build job once. (7) Submit a file to '/ws/JENKINS-58639'. (8) Add a trigger to perforce to slow down syncs. For example create script "sleep.sh":
echo Sleeping for 600s in trigger...
sleep 600
make the file executable, then create a trigger entry:
trigger.sleep.1 command pre-user-sync ./sleep.sh
(9) Run Poll now. Job will wait 5 seconds then start building. (10) Submit another changelist to '/ws/JENKINS-58639'. (11) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building. (12) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building. (13) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building. (14) Wait 20 seconds run Poll now. Job will wait 5 seconds then start building.
Add Comment
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-58456 explain polling per change Change By: Karl Wirth Attachment: image-2019-09-02-16-26-19-383.png 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.200589.1562912637000.4338.1567438020926%40Atlassian.JIRA.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-58456 explain polling per change Change By: Karl Wirth Attachment: image-2019-09-02-16-25-59-683.png 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.200589.1562912637000.4336.1567438020598%40Atlassian.JIRA.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-58456 explain polling per change Change By: Karl Wirth Attachment: image-2019-09-02-16-26-46-699.png 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.200589.1562912637000.4340.1567438020994%40Atlassian.JIRA.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-58456 explain polling per change Change By: Karl Wirth Attachment: image-2019-09-02-16-25-39-289.png 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.200589.1562912637000.4334.1567437960199%40Atlassian.JIRA.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth resolved as Not A Defect Jenkins / JENKINS-58456 explain polling per change Change By: Karl Wirth Status: Open Resolved Resolution: Not A Defect 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.200589.1562912637000.8505.1562917620355%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-58456 explain polling per change 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200589.1562912637000.8507.1562917620383%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-58456 explain polling per change 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200589.1562912637000.8503.1562917620325%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title
Karl Wirth edited a comment on JENKINS-58456
Re: explain polling per change
Hi [~luckyhorang], Yes if you check the Pipeline Syntax snippet generator that checkbox controls incremental (true):!image-2019-07-12-08-35-27-798.png!This is described in: [https://www.perforce.com/manuals/jenkins/Content/P4Jenkins/chapter-polling-build-filters.html?Highlight=poll%20per] *Polling per Change:* A build is carried out for every change that is submitted. The polling event will only return the oldest unbuilt change, resulting in incremental builds. Therefore when enabled you should see: {code:java}CL 1 submitted.5 minute poll builds CL1CL2 submittedCL3 submitted5 minute poll builds CL2CL4 submitted5 minute poll builds CL3{code}As you can see for every change to be built the polling has to occur more frequently than the submits. If you really want on demand builds for every changelist a 'change-submit' Perforce trigger that explicitly calls the Jenkins job URL passing the changelist as a parameter is the recommended mechanism.
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.200589.1562912637000.8501.1562917560159%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth commented on JENKINS-58456 Re: explain polling per change Yes if you check the Pipeline Syntax snippet generator that checkbox controls incremental (true): This is described in: https://www.perforce.com/manuals/jenkins/Content/P4Jenkins/chapter-polling-build-filters.html?Highlight=poll%20per Polling per Change: A build is carried out for every change that is submitted. The polling event will only return the oldest unbuilt change, resulting in incremental builds. Therefore when enabled you should see: CL 1 submitted. 5 minute poll builds CL1 CL2 submitted CL3 submitted 5 minute poll builds CL2 CL4 submitted 5 minute poll builds CL3 As you can see for every change to be built the polling has to occur more frequently than the submits. If you really want on demand builds for every changelist a 'change-submit' Perforce trigger that explicitly calls the Jenkins job URL passing the changelist as a parameter is the recommended mechanism. 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.200589.1562912637000.8499.1562917500508%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-58456 explain polling per change Change By: Karl Wirth Attachment: image-2019-07-12-08-35-27-798.png 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.200589.1562912637000.8493.1562916960121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58456) explain polling per change
Title: Message Title Hokwang Lee created an issue Jenkins / JENKINS-58456 explain polling per change Issue Type: Task Assignee: Unassigned Attachments: image-2019-07-12-15-22-43-852.png Components: p4-plugin Created: 2019-07-12 06:23 Priority: Critical Reporter: Hokwang Lee Hi, I want to make jenkins pipeline job to run whenever commit comes. In checkout code, there's filter: [incremental(true)] feature like below. checkout perforce( credential: 'p4', filter: [incremental(true)], populate: syncOnly(...), workspace: templateSpec(...) ) What is this for? and there's polling build filters options in configuration page. What is this for? What is different with upper code ? Many thanks, Add
