-
Bug
-
Resolution: Duplicate
-
Major
-
None
For historical reasons Windows filesystem is case insensitive (unfortunately). Although the filesystem does store case, frequently the users don't have control over the case of created file/folder names.
Windows users expect all tools to be case agnostic. However, this is not the current situation with Jenkins.
For example, for ArtifactDeployer Plugin on Windows, setting "Artifacts to deploy" to "Foo/**" will deploy nothing if the filesystem folder is called "foo". This is clearly not a behaviour Windows user would expect. Similar issue happens with JUnit Plugin.
The problem root is in the usage of Ant FileSet class which is by default case sensitive (although it can be set to ignore case).
- duplicates
-
JENKINS-5253 artifacts archiving: add option for treating patterns in case insensitive way
-
- Resolved
-
- is related to
-
JENKINS-5253 artifacts archiving: add option for treating patterns in case insensitive way
-
- Resolved
-
Windows can support case sensitive file systems - indeed this is not so unusual with remoteFS - just as much as Linux can support case insensitive file systems.
Whilst some windows users do not expect this, making any changes should be dependant on the underlying File System not the underlying platform (e.g. FAT on Linux should arguably be treated as case insensitive)