[JENKINS-40038] Parameterized Trigger Plug-in broken with Jenkins core 2.33

Parameterized Trigger Plugin 2.32 with "Current build parameters" option was working fine in Jenkins core 2.1.

Upgrading to Jenkins core 2.33 caused this plug-in to fail, the parameters were no longer passed on to the downstream job.

duplicates

JENKINS-34871 After upgrading to Jenkins 2.3 we are unable to trigger parametrized build (SECURITY-170 / CVE-2016-3721)

Gary Smith created issue - 2016-11-25 11:57

Oleg Nenashev made changes - 2017-06-25 21:32

Link

New: This issue duplicates JENKINS-34871 [ JENKINS-34871 ]

Oleg Nenashev made changes - 2017-06-25 21:32

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]

Jenkins