I have been working with Windows-environments for more than 11 years so far and never really thought much about case-sensitivity (PowerShell, cmd and other tools are case-agnostic, for example, Get-Verb or get-VerB both will work fine). However, today I faced with a little issue while configuring multibranch pipeline in Jenkins:
I use the same paths for my jenkinsfile as for other pipelines (that are not multibranched) and that path is consisted of lowercase letters. In fact, if we open an explorer and check the path, my folder is named as “HelloWorld” plus other directories also have uppercase letters. And once I changed the script path to “HelloWorld/Scripts/Jenkinsfile“, the pipeline successfully checked all branches. The possible reason – multibranch pipelines are provided by completely different and apparently case-sensitive plugin. Looks like we should always use case-sensitive values for everything in order to avoid any strange issues. Ok. New rules, new habits 🙂
UseIT | Roman Levchenko 