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

Parameterized Trigger Plugin - doesn't pass parameters after upgrating jenkins to 2.7

      Hi,
      In the last days - I noticed functionality of Parameterized Trigger Plugin has changed and that passing a variable to the triggered job, that is not defined as an input to the triggered job won't be passed.
      Not sure what made this happen, the only change jenkins was upgraded to ver. 2.7
      I created a job named 'B' that triggers a job named 'A', and passes 2 parameters.
      Both jobs do not have input parameters.
      I see that the param.properties file it created and contains the data,
      but for some reason job 'A' doesn't receive the parameters even though this worked in the past.

        1. A.PNG
          A.PNG
          13 kB
        2. B.PNG
          B.PNG
          47 kB
        3. output.PNG
          output.PNG
          29 kB

          [JENKINS-36549] Parameterized Trigger Plugin - doesn't pass parameters after upgrating jenkins to 2.7

          Shawn Zhang added a comment -

          I have the exactly same problem and it's blocking our normal CI running.
          It worked fine before updating to v2.7.1.

          Shawn Zhang added a comment - I have the exactly same problem and it's blocking our normal CI running. It worked fine before updating to v2.7.1.

          Kyle Nehring added a comment -

          I have exactly the same problem, just recently upgraded from 1.625.2 to v2.9

          Kyle Nehring added a comment - I have exactly the same problem, just recently upgraded from 1.625.2 to v2.9

          Kyle Nehring added a comment -

          This is from the SECURITY-170 update.. the current work around to fix this is add the system property to your java_opts

          -Dhudson.model.ParametersAction.keepUndefinedParameters=true

          https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170

          also looks like this plugin wont be fixed according to the page above.

          Kyle Nehring added a comment - This is from the SECURITY-170 update.. the current work around to fix this is add the system property to your java_opts -Dhudson.model.ParametersAction.keepUndefinedParameters=true https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170 also looks like this plugin wont be fixed according to the page above.

            huybrechts huybrechts
            amizrahi Ayelet Mizrahi
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: