The fix for SECURITY-170 as described in this blog post means that Jenkins core filters out any parameters used that were not defined in the job: https://jenkins.io/blog/2016/05/11/security-update/

      Since Stash Pullrequest builder defines lots of parameters at runtime, and then later tries to access them, a bunch of functionality in the plugin fails. See an example resulting failure at https://github.com/nemccarthy/stash-pullrequest-builder-plugin/issues/84

      Presumably this plugin should define its own Action class to store this information, rather than relying on these parameters to be exported into the environment during a build.

      This similar to issue seen in GHPRB plugin.

          [JENKINS-34847] Missing parameters

          Nicholas Brown created issue -
          Nicholas Brown made changes -
          Link New: This issue is related to JENKINS-34762 [ JENKINS-34762 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 171043 ] New: JNJira + In-Review [ 184141 ]
          Nicholas Brown made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Nicholas Brown made changes -
          Link New: This issue is duplicated by JENKINS-37551 [ JENKINS-37551 ]

            nemccarthy nathan m
            nickbrown Nicholas Brown
            Votes:
            8 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: