-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins master v2.70 on Ubuntu 14.04
Jenkins slave on Windows Server 2012 R2
pipeline-utility-steps 1.4.0
The glob parameter of findFiles step accepts wildcard matching pattern, which finds only files matching paths and names in a case-sensitive way.
This is not expected behaviour on Windows slave, where file system is not case sensitive.
[JENKINS-46982] findFiles step does case sensitive matching on Windows slave
This is an issue for me as well.
The only workaround I found is something like this:
findFiles(glob: '*abc*.txt') + findFiles(glob: '*ABC*.txt');
I found this regarding globs (Glob Tool):
Examples:
Zero or More Chars *
One Char ?
Recursive (globstar) **
List {a,b,c}
Range [abc]
Not in Range [!abc]
Not Patterns !(a|b)
Zero or One Pattern ?(a|b)
Zero or More Patterns *(a|b)
One or More Patterns +(a|b)
Exactly One Pattern @(a|b)
That would make it a bit better:
findFiles(glob: '*{a,A}{b,B}{c,C}*.txt'); or findFiles(glob: '*@(a|A)@(b|B)@(c|C)*.txt');
for example, but that is also not working.
David
added a comment - - edited This is an issue for me as well.
The only workaround I found is something like this:
findFiles(glob: '*abc*.txt' ) + findFiles(glob: '*ABC*.txt' );
I found this regarding globs ( Glob Tool ):
Examples:
Zero or More Chars *
One Char ?
Recursive (globstar) **
List {a,b,c}
Range [abc]
Not in Range [!abc]
Not Patterns !(a|b)
Zero or One Pattern ?(a|b)
Zero or More Patterns *(a|b)
One or More Patterns +(a|b)
Exactly One Pattern @(a|b)
That would make it a bit better:
findFiles(glob: '*{a,A}{b,B}{c,C}*.txt' ); or
findFiles(glob: '*@(a|A)@(b|B)@(c|C)*.txt' );
for example, but that is also not working. 
Hi, any update on this issue?