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

Tag match filter shows more entries than direct command (git tag -l "$tagFilter")

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: git-parameter-plugin
    • Labels:
      None
    • Environment:
      OS: Ubuntu 16.04.5 LTS
      Jenkins version: 2.150.1
      Git parameter plugin: 0.9.6
      git command line version: 2.7.4
    • Similar Issues:

      Description

      The help documentation indicates that tag filtering should behave like:
           git tag -l "$tagFilter"

      However, we see different tag lists for the command line git filter versus the plugin filter.

      Example:

      • Git Command:      git tag -l "MTRS-MBP-*"
        • Returns (truncated):
          MTRS-MBP-v02.02.00.RRC05
      • Plugin Filter:         MTRS-MBP-*
        • Returns (truncated):
          MTRS-MBP-v02.02.00.RRC05
          release/MTRS-MBP-v00.03.01.int.1.0.0.2_armhf

      The plugin appears to behave as though "*MTRS-MBP-*" is implied.
      Yet, we have other entries, like "CDR_MTRS-MBP-v01.00.00_Demo", that the plugin does not show.

      The expectation here is that the behavior of the filter follows the stated 'git tag -l' behavior.

       

        Attachments

          Issue Links

            Activity

            kbowen Kevin Bowen created issue -
            kbowen Kevin Bowen made changes -
            Field Original Value New Value
            Description The help documentation indicates that tag filtering should behave like:
                 {{git tag -l "$tagFilter"}}

            However, we see different tag lists for the command line git filter versus the plugin filter.

            Example:
             * Git Command:      git tag -l "MTRS-MBP-*"

             ** _Returns (truncated):_
            MTRS-MBP-v02.02.00.RRC05
             * Plugin Filter:         MTRS-MBP-*
             ** _Returns (truncated):_
            MTRS-MBP-v02.02.00.RRC05
            release/MTRS-MBP-v00.03.01.int.1.0.0.2_armhf

            The plugin appears to behave as though "*MTRS-MBP-*" is implied.
            Yet, we have other entries, like "CDR_MTRS-MBP-v01.00.00_Demo", that the plugin does not show.

            The expectation here is that the behavior of the filter follows the stated 'git tag -l' behavior.

             
            The help documentation indicates that tag filtering should behave like:
                  {{git tag -l "$tagFilter"}}

            However, we see different tag lists for the command line git filter versus the plugin filter.

            Example:
             * Git Command:      git tag -l "MTRS-MBP-*"
             ** _Returns (truncated):_
             MTRS-MBP-v02.02.00.RRC05

             * Plugin Filter:         MTRS-MBP-*

             ** _Returns (truncated):_
             MTRS-MBP-v02.02.00.RRC05
             release/MTRS-MBP-v00.03.01.int.1.0.0.2_armhf

            The plugin appears to behave as though "*MTRS-MBP-*" is implied.
             Yet, we have other entries, like "CDR_MTRS-MBP-v01.00.00_Demo", that the plugin does not show.

            The expectation here is that the behavior of the filter follows the stated 'git tag -l' behavior.

             
            kbowen Kevin Bowen made changes -
            Description The help documentation indicates that tag filtering should behave like:
                  {{git tag -l "$tagFilter"}}

            However, we see different tag lists for the command line git filter versus the plugin filter.

            Example:
             * Git Command:      git tag -l "MTRS-MBP-*"
             ** _Returns (truncated):_
             MTRS-MBP-v02.02.00.RRC05

             * Plugin Filter:         MTRS-MBP-*

             ** _Returns (truncated):_
             MTRS-MBP-v02.02.00.RRC05
             release/MTRS-MBP-v00.03.01.int.1.0.0.2_armhf

            The plugin appears to behave as though "*MTRS-MBP-*" is implied.
             Yet, we have other entries, like "CDR_MTRS-MBP-v01.00.00_Demo", that the plugin does not show.

            The expectation here is that the behavior of the filter follows the stated 'git tag -l' behavior.

             
            The help documentation indicates that tag filtering should behave like:
                  {{git tag -l "$tagFilter"}}

            However, we see different tag lists for the command line git filter versus the plugin filter.

            Example:
             * Git Command:      git tag \-l "MTRS-MBP-*"
             ** _Returns (truncated):_
             MTRS-MBP-v02.02.00.RRC05

             * Plugin Filter:         MTRS-MBP-*

             ** _Returns (truncated):_
             MTRS-MBP-v02.02.00.RRC05
             release/MTRS-MBP-v00.03.01.int.1.0.0.2_armhf

            The plugin appears to behave as though "*MTRS-MBP-*" is implied.
             Yet, we have other entries, like "CDR_MTRS-MBP-v01.00.00_Demo", that the plugin does not show.

            The expectation here is that the behavior of the filter follows the stated 'git tag -l' behavior.

             
            kbowen Kevin Bowen made changes -
            Description The help documentation indicates that tag filtering should behave like:
                  {{git tag -l "$tagFilter"}}

            However, we see different tag lists for the command line git filter versus the plugin filter.

            Example:
             * Git Command:      git tag \-l "MTRS-MBP-*"
             ** _Returns (truncated):_
             MTRS-MBP-v02.02.00.RRC05

             * Plugin Filter:         MTRS-MBP-*

             ** _Returns (truncated):_
             MTRS-MBP-v02.02.00.RRC05
             release/MTRS-MBP-v00.03.01.int.1.0.0.2_armhf

            The plugin appears to behave as though "*MTRS-MBP-*" is implied.
             Yet, we have other entries, like "CDR_MTRS-MBP-v01.00.00_Demo", that the plugin does not show.

            The expectation here is that the behavior of the filter follows the stated 'git tag -l' behavior.

             
            The help documentation indicates that tag filtering should behave like:
                  {{git tag -l "$tagFilter"}}

            However, we see different tag lists for the command line git filter versus the plugin filter.

            Example:
             * Git Command:      git tag \-l "MTRS-MBP-*"
             ** _Returns (truncated):_
             MTRS-MBP-v02.02.00.RRC05

             * Plugin Filter:         MTRS-MBP-*

             ** _Returns (truncated):_
             MTRS-MBP-v02.02.00.RRC05
             release/MTRS-MBP-v00.03.01.int.1.0.0.2_armhf

            The plugin appears to behave as though "\*MTRS-MBP-\*" is implied.
             Yet, we have other entries, like "CDR_MTRS-MBP-v01.00.00_Demo", that the plugin does not show.

            The expectation here is that the behavior of the filter follows the stated 'git tag -l' behavior.

             
            klimas7 Boguslaw Klimas made changes -
            Link This issue depends on JENKINS-40232 [ JENKINS-40232 ]
            klimas7 Boguslaw Klimas made changes -
            Resolution Not A Defect [ 7 ]
            Status Open [ 1 ] Closed [ 6 ]
            kbowen Kevin Bowen made changes -
            Attachment GitParamPluginTagOptions.png [ 45822 ]
            kbowen Kevin Bowen made changes -
            Resolution Not A Defect [ 7 ]
            Status Closed [ 6 ] Reopened [ 4 ]
            klimas7 Boguslaw Klimas made changes -
            Status Reopened [ 4 ] In Progress [ 3 ]
            klimas7 Boguslaw Klimas made changes -
            Issue Type Bug [ 1 ] Improvement [ 4 ]
            klimas7 Boguslaw Klimas made changes -
            Attachment screenshot-1.png [ 46105 ]
            klimas7 Boguslaw Klimas made changes -
            Attachment screenshot-2.png [ 46106 ]
            klimas7 Boguslaw Klimas made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Resolved [ 5 ]

              People

              Assignee:
              klimas7 Boguslaw Klimas
              Reporter:
              kbowen Kevin Bowen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: