[JIRA] [p4-plugin] (JENKINS-32523) P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.
Title: Message Title Paul Allen closed an issue as Fixed Released in 1.3.9 Jenkins / JENKINS-32523 P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce. Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-32523) P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32523 Re: P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce. Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/changes/P4Revision.java src/main/java/org/jenkinsci/plugins/p4/client/ClientHelper.java src/main/java/org/jenkinsci/plugins/p4/tasks/PollTask.java http://jenkins-ci.org/commit/p4-plugin/cad43ac74895c7569ada4c3306731c044d75ce7b Log: Track syncs with a 'Change' field in the Workspace Description. Polling used ‘p4 cstat’ to determine the last sync’ed change in a workspace. However, if the have list is empty (such as in the Force Clean Populate mode) it would appear as if no changes have been synced. JENKINS-32518 JENKINS-32523 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-32523) P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.
Title: Message Title Paul Allen resolved as Fixed Slated for next release Jenkins / JENKINS-32523 P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce. Change By: Paul Allen Status: In Progress Resolved Assignee: Paul Allen Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-32523) P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.
Title: Message Title Paul Allen started work on JENKINS-32523 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-32523) P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.
Title: Message Title Robby Pocase updated an issue Jenkins / JENKINS-32523 P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce. Change By: Robby Pocase Component/s: p4-plugin Component/s: perforce-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-32523) P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.
Title: Message Title Steve Robbins commented on JENKINS-32523 Re: P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce. Are you possibly using "Forced clean and sync"? That option causes this behaviour for me; c.f. JENKINS-32518. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-32523) P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.
Title: Message Title Robby Pocase commented on JENKINS-32523 Re: P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce. I've seen this issue on and off for months now across various jobs. I'm not sure if its specifically related to pending changelists, though. I have a job now that doesn't have any pending changelists (unless there are some in default) that is in the constant queuing state. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-32523) P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.
Title: Message Title Stéphane Pelletier created an issue Jenkins / JENKINS-32523 P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce. Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 19/Jan/16 7:00 PM Environment: Jenkins version: 1.626, P4 Plugin version: 1.3.5 Priority: Major Reporter: Stéphane Pelletier I noticed that the P4 plugin keeps triggering builds on the same Perforce changelist even if no new changelist was submitted to Perforce. I had a look at the polling log and it seems like the "p4 counter change" command is used by the p4 plugin to determine the latest changelist available on Perforce ( see log at the end of this message ). This is probably wrong, since the Perforce doc (https://www.perforce.com/perforce/r12.2/manuals/cmdref/counter.html) says that this command returns "The last changelist number known to the Perforce service (the output of p4 counter change) includes pending changelists created by users, but not yet submitted to the depot. ". This probably explains the bug, since the plugin triggers a build as long as somebody has a pending changelist in his workspace whose changelist number is higher than the last submitted changelist. Started on Jan 19, 2016 1:01:00 PM Polling SCM changes
[JIRA] [p4-plugin] (JENKINS-32523) P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce.
Title: Message Title Stéphane Pelletier updated an issue Jenkins / JENKINS-32523 P4 plugin keeps triggering builds on the same Perforce changelist, even if no new changelist was submitted to Perforce. Change By: Stéphane Pelletier Component/s: perforce-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
