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

Promotion permalinks not offered when job name is parameterized

XMLWordPrintable

      If you specify an upstream job with a promotion process, and select the permalink option, you are able to request a permalink corresponding to the last promotion. (Eventually—for some reason the pulldown does not refresh very reliably so you have to click around a few times to get it to appear.)

      But if the upstream job is defined as $SOME_PARAMETER, the pulldown only shows standard permalinks, so there is no apparent way to request the promotion from the UI.(Presumably you could edit config.xml directly.)

          [JENKINS-22590] Promotion permalinks not offered when job name is parameterized

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-14650 [ JENKINS-14650 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-19007 [ JENKINS-19007 ]

          Jesse Glick added a comment -

          Should this pulldown just be made into an editable combo box? Or text field with completion?

          Jesse Glick added a comment - Should this pulldown just be made into an editable combo box? Or text field with completion?

          Glenn Poston added a comment -

          Id really like to see this fixed. We have a parameterized build that uses the parameter to specify the project name. I would like to be able to copy the artifacts from latest promoted build from that project.

          Also note that editing config.xml directly does not work.

          Glenn Poston added a comment - Id really like to see this fixed. We have a parameterized build that uses the parameter to specify the project name. I would like to be able to copy the artifacts from latest promoted build from that project. Also note that editing config.xml directly does not work.
          Jesse Glick made changes -
          Assignee New: Jesse Glick [ jglick ]
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Jesse Glick added a comment -

          Editing config.xml directly (via POST, for example) does work as a workaround in my experiments.

          Jesse Glick added a comment - Editing config.xml directly (via POST, for example) does work as a workaround in my experiments.

          Jesse Glick added a comment -

          This was merged; maybe JIRA autolinker is dead again.

          Jesse Glick added a comment - This was merged; maybe JIRA autolinker is dead again.
          Jesse Glick made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

            jglick Jesse Glick
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: