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

Change VersionParameterDefinition to simply use property name as the parameter name

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      It's confusing that the property name is not the same as parameter name.
      (This becomes especially painful when using ez-templates.)
      So why concating of group + artifact for the parameter name, and just use the name as the name.?

        Attachments

          Issue Links

            Activity

            brantone Brantone created issue -
            Hide
            tvail Tim Vail added a comment -

            I'd like this too. Keep in mind that changing this could break some other stuff that are, unfortunately, expecting the current setup.

            On the other hand, keeping it this way means that it doesn't look like it is possible to have a job that downloads two different versions of the same artifact.

            Show
            tvail Tim Vail added a comment - I'd like this too. Keep in mind that changing this could break some other stuff that are, unfortunately, expecting the current setup. On the other hand, keeping it this way means that it doesn't look like it is possible to have a job that downloads two different versions of the same artifact.
            rtyler R. Tyler Croy made changes -
            Field Original Value New Value
            Workflow JNJira [ 167082 ] JNJira + In-Review [ 182575 ]
            drekbour Marc Carter made changes -
            Component/s ez-templates-plugin [ 20651 ]
            Hide
            drekbour Marc Carter added a comment -

            If we only consider only the interaction with ez-templates then JENKINS-43731 will introduce an ExtensionPoint allowing individual plugins to control their own templating. This means repository-connector-plugin can synchronise jobs with complete understanding of its own naming patterns.

            If this JIRA has not been implemented by the time the extension point is available, I will rename it and put in a PR

            Show
            drekbour Marc Carter added a comment - If we only consider only the interaction with ez-templates then JENKINS-43731 will introduce an ExtensionPoint allowing individual plugins to control their own templating. This means repository-connector-plugin can synchronise jobs with complete understanding of its own naming patterns. If this JIRA has not been implemented by the time the extension point is available, I will rename it and put in a PR
            drekbour Marc Carter made changes -
            Link This issue is blocked by JENKINS-43731 [ JENKINS-43731 ]
            jgangemi Jae Gangemi made changes -
            Assignee Jae Gangemi [ jgangemi ]
            Hide
            jgangemi Jae Gangemi added a comment -

            fixed in 2.0.0, which will be released in the next few days. please be sure to check the plugin readme before upgrading so you are aware of incompatible changes.

            Show
            jgangemi Jae Gangemi added a comment - fixed in 2.0.0 , which will be released in the next few days. please be sure to check the plugin readme before upgrading so you are aware of incompatible changes.
            jgangemi Jae Gangemi made changes -
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]

              People

              Assignee:
              jgangemi Jae Gangemi
              Reporter:
              brantone Brantone
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: