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

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.

---
Originally reported by wsaxon, imported from: git tag patterns not handled like cli git

• status: Open
  
• priority: Minor
  
• component(s): git-client-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 2
  
• imported: 20251211-071809
  

Raw content of original issue

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.

• environment: git client plugin 1.19.6