When I try to create jobs like
- foo
- FOO
- Foo
- fOo
- ...
Jenkins will only allow me to create the first one. After that, it complains that a job of this name already exists. (It uses the case of the job, I just try to create)
[I'm mildly surprised, because this is Unix, where case matters]
The bad thing comes, when I try to download the job using
http://<jenkins>:<port>/view/Admin/view/All/job/FOO/config.xml
Here I can use whatever case for 'FOO' (e.g. all of the above) and each of the downloads succeed.
I would expect to only be able to download the job with the correct case. (Yielding an error in all other cases)
So what's the bug here? That Jenkins behaves consistently in treating job names case-insensitively?