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

artifacts archiving: add option for treating patterns in case insensitive way

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None

      It would be nice to have option to search artifacts by pattern in case insensitive way.

          [JENKINS-5253] artifacts archiving: add option for treating patterns in case insensitive way

          rutsky created issue -
          mdonohue made changes -
          Component/s New: core [ 15593 ]

          Could someone provide a detailed scenario to understand the requirement? Which search on which page should provide insensitive search? thx

          Dominique Brice added a comment - Could someone provide a detailed scenario to understand the requirement? Which search on which page should provide insensitive search? thx

          Daniel Beck added a comment -

          dominiquebrice: This is about artifact archiving, a post-build step. You specify an Ant-style pattern like

          **/*.hpi

          and apparently that's case sensitive and no way to make it case insensitive.

          Daniel Beck added a comment - dominiquebrice : This is about artifact archiving, a post-build step. You specify an Ant-style pattern like **/*.hpi and apparently that's case sensitive and no way to make it case insensitive.
          Dominique Brice made changes -
          Assignee New: Dominique Brice [ dominiquebrice ]
          Dominique Brice made changes -
          Attachment New: CaseInsensitive.png [ 27788 ]
          Attachment New: CaseSensitive.png [ 27789 ]

          I propose to add a checkbox in the "Advanced..." section of the Artifacts Archiving settings, to indicate whether include and exclude patterns should be considered as case sensitive (default, same behavior as today) or case insensitive (new behavior).

          Dominique Brice added a comment - I propose to add a checkbox in the "Advanced..." section of the Artifacts Archiving settings, to indicate whether include and exclude patterns should be considered as case sensitive (default, same behavior as today) or case insensitive (new behavior).

          Daniel Beck added a comment -

          It's consistent with existing UI, so makes sense.

          A few more options and an approach like Git plugin's additional behaviors would make more sense, but that's still off a bit IMO.

          Daniel Beck added a comment - It's consistent with existing UI, so makes sense. A few more options and an approach like Git plugin's additional behaviors would make more sense, but that's still off a bit IMO.

          Dominique Brice added a comment - - edited

          Pull request created.
          (edited to link new pull request, as first one had a merge conflict)

          Dominique Brice added a comment - - edited Pull request created. (edited to link new pull request, as first one had a merge conflict)

          Daniel Beck added a comment -

          Could the suggestion in the second screen shot be improved to suggest the lowercase file name variant? Or too much effort for too little gain?

          Daniel Beck added a comment - Could the suggestion in the second screen shot be improved to suggest the lowercase file name variant? Or too much effort for too little gain?

            dominiquebrice Dominique Brice
            rutsky rutsky
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: