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

Change VersionParameterDefinition to simply use property name as the parameter name

XMLWordPrintable

      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.?

          [JENKINS-31645] Change VersionParameterDefinition to simply use property name as the parameter name

          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.

          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.

          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

          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

          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.

          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
            brantone Brantone
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: