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

Parameterized variables not being passed to build script

    XMLWordPrintable

Details

    Description

      When creating a multi-configuration job, parameters are not passed as environment variables.

      Screenshot of configuration: http://i.imgur.com/aPmXiXT.png

      Running, as the execute command 'set' (which dumps all environment variables), neither of those are visible (see attached output)

      When trying to view the Params of the submitted job, the panel is blank: http://i.imgur.com/DcwOR5a.png

      Jenkins version is reported as 2.4, installed via RPM from http://pkg.jenkins-ci.org/redhat

      This appears to be a regression with SECURITY-170 - Adding -Dhudson.model.ParametersAction.keepUndefinedParameters=true to JENKINS_JAVA_OPTIONS in /etc/sysconfig/jenkins then make the parameters visible again.

      Note that these Params are explicitly defined in the job, and should not be getting removed.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-34758 Parameters are not passed to child jobs in multi-configuration projects

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            vnkarthik87 KARTHIK VELAYUDHAN added a comment -

            I guess this is an issue related to SECURITY-170 / CVE-2016-3721

            vnkarthik87 KARTHIK VELAYUDHAN added a comment - I guess this is an issue related to SECURITY-170 / CVE-2016-3721
            xrobau Rob Thomas added a comment -

            Confirmed that it is - I edited the description to say adding 'keepUndefinedParameters=true' resolves it, but these are explicitly defined params, as in the screenshot.

            xrobau Rob Thomas added a comment - Confirmed that it is - I edited the description to say adding 'keepUndefinedParameters=true' resolves it, but these are explicitly defined params, as in the screenshot.
            vnkarthik87 KARTHIK VELAYUDHAN added a comment -

            i made it work by restarting the jenkins service in cli, after setting the jenkins java configurations in /etc/sysconfig/jenkins. Even for explicit params.

            vnkarthik87 KARTHIK VELAYUDHAN added a comment - i made it work by restarting the jenkins service in cli, after setting the jenkins java configurations in /etc/sysconfig/jenkins. Even for explicit params.

            People

              Unassigned Unassigned
              xrobau Rob Thomas
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: