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

Use default Release Version Parameter when parameterized build is triggered

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • jira-plugin
    • None

      i.e. when the parameterized build is triggered upstream build no release version is manually selected. Selecting the top one by default works for me.
      Relying on JIRA to set the proper order.

          [JENKINS-19178] Use default Release Version Parameter when parameterized build is triggered

          Christian Lövsund created issue -

          Christian Lövsund added a comment - - edited

          Please review pull request at https://github.com/jenkinsci/jira-plugin/pull/31

          Christian Lövsund added a comment - - edited Please review pull request at https://github.com/jenkinsci/jira-plugin/pull/31

          Christian Lövsund added a comment -

          Changeset: 0bc0a722513e5bd54bb52c10f1fa537749761fcf
          Author: Christian Lovsund
          Date: 2013-08-13 16:03
          Message: Use the first release version as default value.

          Christian Lövsund added a comment - Changeset: 0bc0a722513e5bd54bb52c10f1fa537749761fcf Author: Christian Lovsund Date: 2013-08-13 16:03 Message: Use the first release version as default value.

          Christian Lövsund added a comment -

          BTW, I have used this code on our Jenkins for about a year.

          Christian Lövsund added a comment - BTW, I have used this code on our Jenkins for about a year.

          Radek Antoniuk added a comment -

          I think that relying on JIRA order and defaulting to the first option is not the proper solution for the reasons mentioned in the PR comments...
          If I understood right, for triggering the parameterized build with a parameter this seems like a passing parameter via CLI issue?

          Radek Antoniuk added a comment - I think that relying on JIRA order and defaulting to the first option is not the proper solution for the reasons mentioned in the PR comments... If I understood right, for triggering the parameterized build with a parameter this seems like a passing parameter via CLI issue?

          Radek Antoniuk added a comment -

          Parameterizing build via CLI was added in master (not released yet).

          Radek Antoniuk added a comment - Parameterizing build via CLI was added in master (not released yet).
          Radek Antoniuk made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 150626 ] New: JNJira + In-Review [ 193603 ]
          Radek Antoniuk made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            Unassigned Unassigned
            chrislovsund Christian Lövsund
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: