-
Bug
-
Resolution: Fixed
-
Blocker
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.
- is duplicated by
-
JENKINS-37551 No build parameters are getting set after upgrading to Jenkins 2.7
-
- Closed
-
- is related to
-
JENKINS-34762 PR status cannot be updated due to filtered parameters
-
- Closed
-
[JENKINS-34847] Missing parameters
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 171043 ] | New: JNJira + In-Review [ 184141 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Comment | [ Fixed by https://github.com/nemccarthy/stash-pullrequest-builder-plugin/pull/89 ] |
This bug caught my team when attempting an upgrade to Jenkins. I had to rollback. Definitely a blocker bug, and needs to be addressed ASAP, since I can't find a workaround.