• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • git-client-plugin
    • None
    • git client plugin 1.19.6

      When filtering a list of tags with 'git tag -l' or 'git ls-remote --tags' on the command line, multiple space-delimited patterns may be specified. See git-tag.

      This does not work with the Jenkins git-client-plugin. The pattern list is processed as a single parameter; while using the Git Parameter plugin to try and present a list of tags using two tag patterns, I got no tags.

      According to git-check-ref-format, spaces are not a valid character for git references. So it should be safe to split any passed-in patterns and iterate over them.

          [JENKINS-36864] git tag patterns not handled like cli git

          Will Saxon added a comment - - edited

          Hello @markewaite, I have a patchset for this which I am about to submit a PR for. Will you look at it, or will I need to wait for someone else to discover/grab the issue?

          Will Saxon added a comment - - edited Hello @markewaite, I have a patchset for this which I am about to submit a PR for. Will you look at it, or will I need to wait for someone else to discover/grab the issue?

          Mark Waite added a comment -

          I'm the one who will look at it. I have a large backlog of other pull requests to evaluate, and am targeting to release Jacob Keller's work on submodule authentication in time for Jenkins World 2016 (Sep 2016). Thus, it may be a month or two before I evaluate the pull request.

          You can increase the chances of my evaluating the pull request by writing tests of the modified methods, by not making white space changes, and by assuring that the plugin behaves well with your changes during interactive testing.

          Mark Waite added a comment - I'm the one who will look at it. I have a large backlog of other pull requests to evaluate, and am targeting to release Jacob Keller's work on submodule authentication in time for Jenkins World 2016 (Sep 2016). Thus, it may be a month or two before I evaluate the pull request. You can increase the chances of my evaluating the pull request by writing tests of the modified methods, by not making white space changes, and by assuring that the plugin behaves well with your changes during interactive testing.

            Unassigned Unassigned
            wsaxon Will Saxon
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: