[JIRA] (JENKINS-58067) Explain why duplicate syncIDs are a problem
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-58067 Explain why duplicate syncIDs are a problem Change By: Karl Wirth Labels: P4_C P4_B P4_VERIFY 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.200091.1560856096000.4144.1567412100585%40Atlassian.JIRA.
[JIRA] (JENKINS-58067) Explain why duplicate syncIDs are a problem
Title: Message Title Karl Wirth commented on JENKINS-58067 Re: Explain why duplicate syncIDs are a problem Hi Kris Conklin - Thanks for the feeback. I will up the priority on this one to flag it to the developers. 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.200091.1560856096000.4142.1567412100441%40Atlassian.JIRA.
[JIRA] (JENKINS-58067) Explain why duplicate syncIDs are a problem
Title: Message Title Kris Conklin commented on JENKINS-58067 Re: Explain why duplicate syncIDs are a problem I have seen these errors for a long time in my logs but this is the first time ive actually understood why, so I would agree a better error text would be very helpful. 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.200091.1560856096000.3441.1567193760155%40Atlassian.JIRA.
[JIRA] (JENKINS-58067) Explain why duplicate syncIDs are a problem
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-58067 Explain why duplicate syncIDs are a problem Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2019-06-18 11:08 Environment: 1.10.0 Labels: P4_C Priority: Minor Reporter: Karl Wirth In the polling log the message 'duplicate syncID found' can be raised: P4: Polling on: master with:jenkins-master-TestJobName-0 WARNING: duplicate syncID found: jenkins-NODE_NAME-TestJobName-EXECUTOR_NUMBER Found last change 563 on syncID jenkins-NODE_NAME-TestJobName-EXECUTOR_NUMBER Found last change 581 on syncID jenkins-NODE_NAME-TestJobName-EXECUTOR_NUMBER ... p4 client -o jenkins-master-JENKINS-TestJobName-0 + This is related to: https://www.perforce.com/manuals/jenkins/Content/P4Jenkins/pipeline-script-setup.html#Advanced_Polling When polling the plugin needs a way to know what has changed since the last job. This is done by stripping the generic variables from the workspace name then saving the last synced changelist number as a 'SyncID' and storing it in the 'build.xml' on the Jenkins master. If the workspace name is reused in the same job, but with a different view this could cause the highest changelist to be different and may cause the polling to miss new changes. Therefore
