I've added `-Dhudson.model.ParametersAction.safeParameters=MVN_RELEASE_VERSION,MVN_DEV_VERSION,MVN_ISDRYRUN` to the variable `JENKINS_JAVA_OPTIONS` in config file /etc/sysconfig/jenkins, that fixed it.
Thanks for your help! Am Donnerstag, 12. Mai 2016 17:29:48 UTC+2 schrieb matthew...@diamond.ac.uk: > > Set `-Dhudson.model.ParametersAction.keepUndefinedParameters`=true to > allow undefined parameters to be injected as environment variables or > `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to > whitelist specific parameter names, even though it represents a security > breach > > > > *From:* jenkins...@googlegroups.com <javascript:> [mailto: > jenkins...@googlegroups.com <javascript:>] *On Behalf Of *Daniel Hiller > *Sent:* 12 May 2016 16:28 > *To:* Jenkins Users > *Subject:* Re: $MVN_RELEASE_VERSION missing after Upgrade to Jenkins 2 > > > > Hi again, > > just found this JIRA issue: > https://issues.jenkins-ci.org/browse/JENKINS-12128 > > There it is clearly stated that these variables are exposed. Now I don't > understand what I have to change to be able to access them again? > > Regards, > Daniel > > Am Donnerstag, 12. Mai 2016 17:21:48 UTC+2 schrieb Daniel Hiller: > > Hi all, > > I've made the step to upgrading our jenkins server from 1632 to > 2.3.whatever (hooray!) and everything seems to work fine except one thing: > > looks like environment variable $MVN_RELEASE_VERSION is not set during the > build when using the M2 release plugin. I don't know how or why it was set > (didn't find any documentation about that) but what I know is that it used > to work in 1.632 (we relied on this magic setting where we found the > release version number) > > Now I don't want it back, I just want to know who was responsible for > setting it and how I can re-set this variable so that everything will work > again. Can anybody shed sone light on this here please? > > Thanks for your time, > > Daniel > > -- > 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 jenkinsci-use...@googlegroups.com <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/9a5aefbf-a040-4f8d-9c3c-855f89bc6ff1%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-users/9a5aefbf-a040-4f8d-9c3c-855f89bc6ff1%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > > -- > > This e-mail and any attachments may contain confidential, copyright and or > privileged material, and are for the use of the intended addressee only. If > you are not the intended addressee or an authorised recipient of the > addressee please notify us of receipt by returning the e-mail and do not > use, copy, retain, distribute or disclose the information in or attached to > the e-mail. > Any opinions expressed within this e-mail are those of the individual and > not necessarily of Diamond Light Source Ltd. > Diamond Light Source Ltd. cannot guarantee that this e-mail or any > attachments are free from viruses and we cannot accept liability for any > damage which you may sustain as a result of software viruses which may be > transmitted in or with the message. > Diamond Light Source Limited (company no. 4375679). Registered in England > and Wales with its registered office at Diamond House, Harwell Science and > Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom > > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4a5e3bbf-d7f9-4bd3-bbc3-c42d55c6cd50%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
