[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis closed an issue as Fixed Fixed in 1.4.8. Thank you! Jenkins / JENKINS-36883 Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Change By: Jason Davis Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis edited a comment on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Fixed Verified fixed in 1.4.8. Thank you! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java 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/AbstractTask.java src/main/java/org/jenkinsci/plugins/p4/tasks/CheckoutTask.java src/main/java/org/jenkinsci/plugins/p4/tasks/PollTask.java src/test/java/org/jenkinsci/plugins/p4/client/ConnectionTest.java http://jenkins-ci.org/commit/p4-plugin/f4c24f7964bd1de847ace7b43546be81e51d2ccc Log: Polling Fix for use with quiet period. Switched all uses of change/label to P4Revision object and implemented Comparable. The changes to build are now calculated at build time (after the quiet period) not during the polling phase. JENKINS-36883 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Paul Allen started work on JENKINS-36883 Change By: Paul Allen Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Karl Wirth commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Have reproduced this (ignoring the 'now' label for this example). Setup a polling period of 2 minutes but a Quiet setting on the job of 3 minutes. The job will run with the latest polled changelist of the 2 polls. For example: Poll 1 determines changelist 256 is the latest - triggers job#36 with a quiet period of 3 mins. 3 more changes made after quiet period starts and before next poll period. CL=260 on included branch, 261 and 262 on excluded from poll branch. Poll 2 determines that changelist 260 is the latest. Job#36 runs with changelist 260 as the latest changelist. So the `bug` is that the running job picks up the latest poll CL not the poll CL that was available when the job was started. Note that this is not the latest CL in the workspace because there were later CLs on the branch that was excluded from the polling filter. Attaching JENKINS-36883-repro.txt full log output. The desired behavior of putting 'now' in the 'Pin build at Perforce label' field would get up to 262 which is the desired behavior. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-36883 Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Change By: Karl Wirth Attachment: JENKINS-36883-repro.txt Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Hi Paul - I agree with you that the polling filter should only prevent builds from occurring on the changes in the filter path! That feature is working wonderfully, but there’s something else going on that’s causing files in the workspace spec to be sync’ed to _different _changelist levels after the Jenkins Quiet Period - and that started happening with v1.3.9 of the plugin. Up through 1.3.8, ALL files in a workspace spec did sync to the latest CL after a Quiet Period at build start time (without @now) – but that’s not happening any longer. Please see the above example. I explain there that, right now and without the use of @now in the workspace spec or P4 label setting, non-filtered files are currently being sync'ed to latest (CL 105), while filtered files are being sync'ed to trigger level (CL 100 instead of CL 103). I’ve confirmed this by testing with the above spec in a simple Jenkins job. Just make some checkins to files both in and out of a filtered path during a Quiet Period to see that they’re not synced to the latest CL at build start time. You suggested above in the Sept. 8 comment, that the build should sync to the CL at trigger time - not the CL at start time, so that other changes don't sneak in to the changes report. Also that @now should be used as a workaround. I’m further suggesting that @now shouldn’t be required to make the filtered files sync to latest at build start, because Jenkins has a configurable Quiet Period setting, which by design is to enable Devs to submit other changes after a trigger as an "oops" measure. If @now becomes required in the P4 Plugin label field or workspace spec to sync to latest after a Quiet Period, then that prevents use of other P4 labels I might like to use, essentially states that more configuration is required to use the Jenkins Quiet Period setting, would make the P4 plugin work by differently than all other SCM plugins I’m familiar with since I started using Jenkins around 8-9 years ago (TFS, SVN, Community Perforce), and the P4 plugin itself did not have this requirement until v1.3.9. In the end, I'm first hoping that ALL the files in the workspace spec are synced to the same and latest CL at build start time like it once did (and that’s the same CL that the changes also report uses) – and second, that the build should not require @now to deal with those changes checked in during the Jenkins Quiet Period because I believe that alters what one would expect from SCM plugins when using a Quiet Period (as well as other reasons mentioned in the above comments). Add Comment
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Paul Allen commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Think I am misunderstanding something, or your environment is different to mine. All files should get sync'ed to @now (the latest change). If you look in the log output you should see p4 sync ///...@now. "Exclude Changes from Depot Path" is only a polling filter to prevent build events from occurring on changes in the specified path. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis reopened an issue Please - before closing - reconsider that not syncing all files in a workspace spec to latest by default goes philosophically against the quiet period, and that currently (without the now label), the build is syncing non-filtered files to the latest changelist, while filtered files in the workspace spec are syncing to a different, earlier changelist, which is not the same behavior (tried to explain better in my last comment). Jenkins / JENKINS-36883 Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Change By: Jason Davis Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title
Jason Davis commented on JENKINS-36883
Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
OK - however, I'm not certain this is a good fix for the problem. Changes after a trigger should be allowed during a quiet period without requiring the now label - not doing so thwarts the purpose of having a quiet period in Jenkins. Additionally, files are in fact being synced to different changeset levels at build start time. For ex. here's a contrived workspace spec in Jenkins: //SCM/Tools/Test/... //$ {JOB_NAME}/SCM/Tools/Test/... "//SCM/buildinfo/..." "//${JOB_NAME} /buildinfo/..." then I "Exclude Changes from Depot Path" with this: //SCM/buildinfo Next:
A build is triggered by a change under //SCM/Tools/Test, let's say with changeset 100.
Quiet period starts. During the quiet period, changes 101 through 105 are checked in, with 103 being the last change in the /buildinfo/... path and 105 being the last change under the Tools/Test/... path
The quiet period ends.
The build launches - the latest available changeset for the workspace is 105. What is occurring is that the build is sync'ing the files changed during the quiet period under Tools/Test/... to changeset 105 and the files changed under buildinfo/... to changeset 100. I've confirmed this with a simple Jenkins job using the above spec and a quiet period. This is inconsistent - the files in buildinfo/... should be synced to the latest changeset for the whole workspace (105) at build time without the use of the now label, or everything should be synced to changeset 100, however, I'd argue syncing to changeset 100 would runs against the purpose of the quiet period AND is not what occurred through v1.3.8 of the plugin: all files in the workspace spec were synced to the latest at build time.
My hope is that everything in the workspace spec would be synced to the latest at build time (unless you use Polling per Change), because that would be consistent no matter how the build was launched.
Add Comment
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Paul Allen commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Yes the change is to allow 'now' to always sync to the latest, at the point of sync and not when the build was scheduled. If you specify any other label or change then that is what will get synced. The Polling Filter for excluded files is only to decide to when to build and not how to sync. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Thanks a ton for working on this! It sounds like perhaps the change was to enable 'now' work as a label after a quiet period. Is that the only change in the works, or will exclude filtered files now also be synced to the latest change without the label? I could update all my jobs to use 'now', but then I'd have to use that by default when using the plugin (to accommodate the excluded files + quiet period problem) and it makes me wonder what I should do if I ever need to use the plugin with a different label other than 'now'. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Paul Allen resolved as Fixed Ready for release Jenkins / JENKINS-36883 Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Change By: Paul Allen Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/client/ClientHelper.java src/main/java/org/jenkinsci/plugins/p4/tasks/CheckoutTask.java http://jenkins-ci.org/commit/p4-plugin/7cef2cab7ee612349b743bcf86ab186a6f74b27e Log: Change 'now' to the latest change at the point of sync. JENKINS-36883 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Paul Allen - hope the conference was a good one for you. Just curious if I helped make the issue more clear. Fingers crossed that you have time to take a look and help (I think it's just a problem with files in the excluded list not syncing to the latest due to the quiet period). If I can test or do anything, just let me know. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Tested pinning the build to a label with both 'now' and '@now' with v1.4.6. Unfortunately, still getting the same behavior - files in the exclude changes filter are not being sync'ed to the latest changeset if additional changes are checked in during the quiet period, but the other files in the view are. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Thanks for taking a look! I have not tried the pin label to 'now' idea (that idea just didn't dawn on me. ), but I'll give that a try ASAP and let you know. I can understand your point of view for knowing what triggered the build, but at the same time, when the build finally fires off after a quiet period, just taking the latest available change when the build finally fires off, and tracking _that _for the changes summary, I would suggest makes sense also. Say there was no quiet period or polling. If someone pushed the build now button, Perforce would gather the latest changeset at that moment and sync to that level. Polling without a quiet period also ends up syncing to the latest available changeset at build launch. It's the addition of the quiet period that is leading to different behavior, because other changes checked in after the trigger, but before the build launches (which of course is one purpose for the quiet period - in case the Devs have an "oh crap! I forgot to check that in also" moment) are being sync'ed to changeset that triggered the build, not the latest. If - no matter how you triggered the build - the build always synced and tracked to the latest changeset, the summary would be consistent no matter how the build is launched. This would be how the community plugin worked and the P4 plugin worked up through 1.3.8. It also maintains the purpose of the quiet period, otherwise the "oh crap!" changes never make it into the build, because they are checked in after the trigger changeset. Also – and this is the big thing that threw me off – it's only the files that are in the "Exclude Changes" filter that are being sync'ed to the trigger changeset level. Normal files in the view, but not in the Exclude Changes filter, are being synced to the latest available changeset at build launch. In my environment, more changes are often checked in during the quiet period, and unfortunately, the way our builds communicate, those Exclude Changes files must be the latest available at build launch time, or hell breaks loose. Thanks and hope you enjoy the conference! Add Comment
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Paul Allen started work on JENKINS-36883 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Paul Allen commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time If I understand your issue fully this is by design... When a build is kicked off I want to establish what triggered the build and record it for the build summary. If the build is delayed I didn't want later changes sneaking in under the radar. These later changes should get delayed for the next build. In other words when a build is triggered, at that instance of time, that is what is going to get built. I'm about to fly out to the Jenkins Conference (I live in the UK, so thought I'd spend a few extra days in San Francisco). It will be a few weeks before I'm back in the office, but will try and take a look at the code and see if there is something that might work for you. It's a bit of a long shot, but have you tried setting the 'Pin build at Perforce Label' to 'now'. The label 'now' means the latest change, depending on when this gets evaluated it might help. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-36883 Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Change By: Paul Allen Assignee: Paul Allen Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis edited a comment on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Unfortunately, syncing to latest is still not working in version 1.4.6. Also tried the new option to "Exclude changes outside view mask" and that too also left me with files outside the view mask that were not synced to the latest at build time. Files within the mask do sync to the latest are being synced to the latest if subsequent check-ins occur during the quiet period. I just don't understand how not syncing (even the filtered paths) to the latest at build time is expected behavior. If I could fix this on my own I would... Something in 1.3.9 that wasn't considered? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Unfortunately, syncing to latest is still not working in version 1.4.6. Also tried the new option to "Exclude changes outside view mask" and that too also left me with files outside the view mask that were not synced to the latest at build time. Files within the mask do sync to the latest are synced to the latest if subsequent check-ins occur during the quiet period. I just don't understand how not syncing (even the filtered paths) to the latest at build time is expected behavior. If I could fix this on my own I would... Something in 1.3.9 that wasn't considered? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Man - I was hoping that version 1.4.4's change for JENKINS-37124 was going to address this problem also, but files in the "exclude changes..." list are still being synced to the triggered changelist number and not the latest available changelist. It's a bummer, because I'd like to stay in sync with the other fixes, improvements, and changes for building pipelines. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-36883 Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Change By: Jason Davis Environment: P4 2015.2 (Win 2008 R@), Jenkins 2.14 (Win 2008 R2), P4-Plugin 1.4.3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Possibly also related to: JENKINS-33484 - P4 sync on triggered builds ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis created an issue Jenkins / JENKINS-36883 Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Jul/22 6:37 PM Priority: Major Reporter: Jason Davis I’ve found that the latest versions of files that are mapped in a workspace and also in an “Exclude changes from Depot path” polling filter, are not being synced at build time. Here’s the scenario. I’m currently set Jobs to use Manual workspaces set in Jenkins, to do a Force Sync, and have the “Populate have list” flag set. The Workspace includes an example path: PathA/… PathB/… Also configured with the Polling Filter - “Exclude changes from Depot path” is set to a path under PathB (actually in my test it was the same path). What happens: A check-in under Path A is recognized from polling and triggers a build which has a quiet period associated with it. During the quiet period, one or more check-ins occur under Path B. These files naturally have a higher changelist number than what triggered the build. When the quiet period expires, the build starts and syncs Path A’s files to latest available changelist for that Path, whatever it may be – All is good! For the files in Path B, however, the build syncs to the changelist number from Path A that triggered the build, NOT the latest available changelist. That causes the files under Path B, to be sync’ed to non-latest state. Again, if check-ins occur in the quiet period under Path A – the latest versions of those files ARE being synced.
