Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-37761

case in spelling of jobname doesn't matter on downloadign using wget

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Won't Fix
    • Component/s: core
    • Labels:
    • Environment:
      Jenkins 2.17 running on RH Linux
    • Similar Issues:

      Description

      When I try to create jobs like

      1. foo
      2. FOO
      3. Foo
      4. fOo
      5. ...
        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)

        Attachments

          Activity

          martinjost Martin Jost created issue -
          danielbeck Daniel Beck made changes -
          Field Original Value New Value
          Resolution Won't Fix [ 2 ]
          Status Open [ 1 ] Resolved [ 5 ]

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            martinjost Martin Jost
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: