We just upgraded our Jenkins from 1.642.3 to 2.7.4 and with that issue
in mind, we did add the keepUndefinedParameters=true. We haven't seen
any problems. We do have some jobs that trigger a downstream job with
parameters from a properties file. Is that what you're doing? Or are you
using "Inject environment variables to the build process", using a
properties file, in the downstream job? Or something else?
Eric
On 10/3/2016 1:15 PM, Steve K wrote:
Eric, I think you're right. My problem is caused by the new security
policies.
I have not found the right combination of settings to make things work
as before.
I tried starting Jenkins with
-Dhudson.model.ParametersActon.keepUndefinedParameters=true, but that
did not solve the problem.
Have you needed to make similar adjustments?
Thanks.
--
You received this message because you are subscribed to the Google
Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/abaee195-c7b3-43b8-b46c-50a59f7ec787%40googlegroups.com
<https://groups.google.com/d/msgid/jenkinsci-users/abaee195-c7b3-43b8-b46c-50a59f7ec787%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
*Eric Pyle
*
Release Engineer
Lebanon
+1 603-277-3060 (T)
+1 603-359-8670 (M)
[email protected] <mailto:[email protected]>
http://www.cd-adapco.com <http://www.cd-adapco.com>
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/a2ef4667-f60b-5a53-25b8-ab574716cbc3%40cd-adapco.com.
For more options, visit https://groups.google.com/d/optout.
