Polling build filters are case sensitive when connected to a case insensitive server.
For example if the polling build filter is '//depot/sub' submitting '//depot/sub/f1' will be ignored but submitting '//depot/SUB/f1' will trigger a build.
Note this behavior on a Linux client. If I create a directory called SUB and sync when connected to a C1 server this is what I see:
$ cd SUB $ p4 sync ... //depot/SUB/f10#1 - added as /wsC1/SUB/f10 //depot/sub/f6#1 - added as /wsC1/SUB/f6 //depot/sub/f7#1 - added as /wsC1/SUB/f7 //depot/sub/f9#1 - added as /wsC1/SUB/f9
Note that in depot syntax files in SUB and sub are treated the same.
Reproduction Steps:
(1) Start a Perforce server with the -C1 flag:
p4d -r /p1/1/root -L log -C1 -p 1666
(2) Create a 'jenkins' users in this P4D.
(3) Create a workspace on a Linux box and submit the file '//depot/sub/f1'.
(4) Create a Jenkins polled job with a workspace view of '//depot/... ${P4_CLIENT}/...'.
(5) Add the polling build filter:
//depot/sub
(6) Run the job once.
(7) Submit the file '//depot/sub/f2'.
(8) Run 'Poll Now'. The build is not triggered.
(9) Remove the files from the workspace using:
p4 sync //...#0
(10) Rename the folder 'sub' to be 'SUB'.
(11) Submit the file '//depot/SUB/f3'.
(12) Run 'Poll Now'. The build IS not triggered.
Expected Behavior:
The build is not triggered.
Workaround:
Need to add every possible variation of the path's case to the polling build filter.
- is related to
-
JENKINS-48584 Add case insensitive option for "Exclued changes from Depot path"
-
- Open
-
p4karl I think this is a duplicate of the one I opened a while back?
https://issues.jenkins-ci.org/browse/JENKINS-48584