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

predefined params no longer propogate in parameterized-trigger

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I use the parameterized-trigger plugin to trigger a sequence of about 10 jobs.
      I noticed when I upgraded to version 2.0 of the plugin, that my downstream
      builds lost the predefined parameter values set in the first job.

      I setup a simple test that used to work in an older version of the plugin:
      3 jobs: test1 triggers test2 which triggers test3. I have a predefined var in
      test1. I can echo is successfully in the test2 job, but in test3 the variable
      is not set.

        Attachments

          Activity

          Hide
          adphillips adphillips added a comment -

          PS I tried setting a user-specified var in the test1 job and it does in fact
          make it all the way to test3. Only predefined params seem to not progate, they
          only are availble to the direct dependency of the job in which they are specified.

          Show
          adphillips adphillips added a comment - PS I tried setting a user-specified var in the test1 job and it does in fact make it all the way to test3. Only predefined params seem to not progate, they only are availble to the direct dependency of the job in which they are specified.
          Hide
          mindless Alan Harder added a comment -

          Can you explain in more detail? Guess I'm not sure what predefined vs user-specified parameters are.. here's what I tried:
          test1 triggers test2 with "Current Build Parameters"
          test1 has 1 choice parameter
          test2 triggers test3 with "Current Build Parameters"
          test2 itself has no defined parameters

          I ran a build of test1 and when test3 runs I can see the "Parameters" link in the sidepanel of that build and it shows the parameter.

          Show
          mindless Alan Harder added a comment - Can you explain in more detail? Guess I'm not sure what predefined vs user-specified parameters are.. here's what I tried: test1 triggers test2 with "Current Build Parameters" test1 has 1 choice parameter test2 triggers test3 with "Current Build Parameters" test2 itself has no defined parameters I ran a build of test1 and when test3 runs I can see the "Parameters" link in the sidepanel of that build and it shows the parameter.
          Hide
          mindless Alan Harder added a comment -

          sorry, not too familiar with this plugin yet.. I added a "Predefined Parameters" item (in addition to the "Current Build Parameters" item) for test1.
          Now for the build in test2 I see two "Parameters" links in the sidepanel for that build.. clicking either one shows the choice parameter from test1, but in build.xml for the build I can see the predefined params are there).
          test3 got only the choice parameter.

          I think the problem here is the "Current Build Parameters" and "Predefined Parameters" were added to test2's build as separate ParametersActions instead of combining into one.

          Show
          mindless Alan Harder added a comment - sorry, not too familiar with this plugin yet.. I added a "Predefined Parameters" item (in addition to the "Current Build Parameters" item) for test1. Now for the build in test2 I see two "Parameters" links in the sidepanel for that build.. clicking either one shows the choice parameter from test1, but in build.xml for the build I can see the predefined params are there). test3 got only the choice parameter. I think the problem here is the "Current Build Parameters" and "Predefined Parameters" were added to test2's build as separate ParametersActions instead of combining into one.
          Hide
          mdonohue mdonohue added a comment -

          The double Parameters link issue is documented in JENKINS-5143

          Show
          mdonohue mdonohue added a comment - The double Parameters link issue is documented in JENKINS-5143
          Hide
          peter_schuetze peter_schuetze added a comment -

          I ran into the same problem which prompted me to log JENKINS-5143. I needed to use the "Predefined Parameters" since I needed to pass parameters from test2 to test3 that where not known in test1. However, for security reasons I enter credentials in test1 and pass them through test2 to test3. I tried to pass the password from test2 to test3 using "Predefined Parameters", but the password would be shown than in test3 under the password link. So I need to pass them as "Current Build Parameters".

          Therefore I need to use "Current Build Parameters" and "Predefined Parameters".

          Show
          peter_schuetze peter_schuetze added a comment - I ran into the same problem which prompted me to log JENKINS-5143 . I needed to use the "Predefined Parameters" since I needed to pass parameters from test2 to test3 that where not known in test1. However, for security reasons I enter credentials in test1 and pass them through test2 to test3. I tried to pass the password from test2 to test3 using "Predefined Parameters", but the password would be shown than in test3 under the password link. So I need to pass them as "Current Build Parameters". Therefore I need to use "Current Build Parameters" and "Predefined Parameters".
          Hide
          mindless Alan Harder added a comment -

          Marking this issue as resolved, as I believe the root cause is fixed in release 2.3 (now available).. reopen if not, thanks.

          Show
          mindless Alan Harder added a comment - Marking this issue as resolved, as I believe the root cause is fixed in release 2.3 (now available).. reopen if not, thanks.

            People

            • Assignee:
              mindless Alan Harder
              Reporter:
              adphillips adphillips
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: